docs: Update configmap docs for enable-global-auth option (#10667)
* docs: Include default annotation prefix is docs Most docs includes the annotation prefix * docs: Update annotations docs for global-auth Correct documentation to reflect whats possible. It is not possible to use `enable-global-auth: false` in ConfigMap.
This commit is contained in:
parent
a7c40bbec4
commit
cd3e5d323d
2 changed files with 3 additions and 3 deletions
|
@ -529,7 +529,7 @@ Since version 1.9.0, `"auth-snippet"` annotation is disabled by default and has
|
|||
|
||||
#### Global External Authentication
|
||||
|
||||
By default the controller redirects all requests to an existing service that provides authentication if `global-auth-url` is set in the NGINX ConfigMap. If you want to disable this behavior for that ingress, you can use `enable-global-auth: "false"` in the NGINX ConfigMap.
|
||||
By default the controller redirects all requests to an existing service that provides authentication if `global-auth-url` is set in the NGINX ConfigMap. If you want to disable this behavior for a specific ingress, you can use the annotation `nginx.ingress.kubernetes.io/enable-global-auth: "false"`.
|
||||
`nginx.ingress.kubernetes.io/enable-global-auth`:
|
||||
indicates if GlobalExternalAuth configuration should be applied or not to this Ingress rule. Default values is set to `"true"`.
|
||||
|
||||
|
@ -1008,4 +1008,4 @@ metadata:
|
|||
```
|
||||
|
||||
!!! attention
|
||||
Since version 1.9.0, `"stream-snippet"` annotation is disabled by default and has to be explicitly enabled, see [allow-snippet-annotations](./configmap.md#allow-snippet-annotations). Enabling it can be dangerous in multi-tenant clusters, as it can lead to people with otherwise limited permissions being able to retrieve all secrets on the cluster. See CVE-2021-25742 and the [related issue on github](https://github.com/kubernetes/ingress-nginx/issues/7837) for more information.
|
||||
Since version 1.9.0, `"stream-snippet"` annotation is disabled by default and has to be explicitly enabled, see [allow-snippet-annotations](./configmap.md#allow-snippet-annotations). Enabling it can be dangerous in multi-tenant clusters, as it can lead to people with otherwise limited permissions being able to retrieve all secrets on the cluster. See CVE-2021-25742 and the [related issue on github](https://github.com/kubernetes/ingress-nginx/issues/7837) for more information.
|
||||
|
|
|
@ -1298,7 +1298,7 @@ _**default:**_ "/.well-known/acme-challenge"
|
|||
|
||||
A url to an existing service that provides authentication for all the locations.
|
||||
Similar to the Ingress rule annotation `nginx.ingress.kubernetes.io/auth-url`.
|
||||
Locations that should not get authenticated can be listed using `no-auth-locations` See [no-auth-locations](#no-auth-locations). In addition, each service can be excluded from authentication via annotation `enable-global-auth` set to "false".
|
||||
Locations that should not get authenticated can be listed using `no-auth-locations` See [no-auth-locations](#no-auth-locations). In addition, each service can be excluded from authentication via annotation `nginx.ingress.kubernetes.io/enable-global-auth` set to "false".
|
||||
_**default:**_ ""
|
||||
|
||||
_References:_ [https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#external-authentication](https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#external-authentication)
|
||||
|
|
Loading…
Reference in a new issue