public_git
/
postgres-operator
mirror of https://github.com/zalando/postgres-operator.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: fix typo in option name for cross-ns secrets (#1650)

This commit is contained in:
Luc Ritchie 2021-10-25 10:18:51 -04:00 committed by GitHub
parent 720b4575c7
commit d20f511e44
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/cluster_manifest.md
View File

@ -110,7 +110,7 @@ These parameters are grouped directly under the `spec` key in the manifest.
`CREATEDB`, `BYPASSURL`. A login user is created by default unless NOLOGIN is `CREATEDB`, `BYPASSURL`. A login user is created by default unless NOLOGIN is
specified, in which case the operator creates a role. One can specify empty specified, in which case the operator creates a role. One can specify empty
flags by providing a JSON empty array '*[]*'. If the config option flags by providing a JSON empty array '*[]*'. If the config option
`enable_cross_namespace_secrets` is enabled you can specify the namespace in `enable_cross_namespace_secret` is enabled you can specify the namespace in
the user name in the form `{namespace}.{username}` and the operator will the user name in the form `{namespace}.{username}` and the operator will
create the K8s secret in that namespace. The part after the first `.` is create the K8s secret in that namespace. The part after the first `.` is
considered to be the user name. Optional. considered to be the user name. Optional.
@ -215,7 +215,7 @@ information, see [user docs](../user.md#prepared-databases-with-roles-and-defaul
* **secretNamespace** * **secretNamespace**
for each default LOGIN role the operator will create a secret. You can for each default LOGIN role the operator will create a secret. You can
specify the namespace in which these secrets will get created, if specify the namespace in which these secrets will get created, if
`enable_cross_namespace_secrets` is set to `true` in the config. Otherwise, `enable_cross_namespace_secret` is set to `true` in the config. Otherwise,
the cluster namespace is used. the cluster namespace is used.
## Postgres parameters ## Postgres parameters

2
docs/reference/operator_parameters.md
View File

@ -264,7 +264,7 @@ configuration they are grouped under the `kubernetes` key.
[admin docs](../administrator.md#pod-disruption-budget) for more information. [admin docs](../administrator.md#pod-disruption-budget) for more information.
Default is true. Default is true.
* **enable_cross_namespace_secrets** * **enable_cross_namespace_secret**
To allow secrets in a different namespace other than the Postgres cluster To allow secrets in a different namespace other than the Postgres cluster
namespace. Once enabled, specify the namespace in the user name under the namespace. Once enabled, specify the namespace in the user name under the
`users` section in the form `{namespace}.{username}`. The default is `false`. `users` section in the form `{namespace}.{username}`. The default is `false`.