Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
postgres-operator
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
GitHub Mirror
zalando
postgres-operator
Commits
deec6c64
Unverified
Commit
deec6c64
authored
4 years ago
by
Rafia Sabih
Committed by
GitHub
4 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Update docs/reference/operator_parameters.md
Co-authored-by:
Felix Kunde
<
felix-kunde@gmx.de
>
parent
8cd0c954
Branches
Branches containing commit
Tags
v0.14.2
Tags containing commit
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/reference/operator_parameters.md
+5
-5
5 additions, 5 deletions
docs/reference/operator_parameters.md
with
5 additions
and
5 deletions
docs/reference/operator_parameters.md
+
5
−
5
View file @
deec6c64
...
...
@@ -265,11 +265,11 @@ configuration they are grouped under the `kubernetes` key.
Default is true.
*
**enable_cross_namespace_secrets**
To
create
secrets in a different namespace other than the
cluster namespace,
e
na
ble this option
. Once
,
enabled
user names of the intented users are to b
e
provided with the namespace
in the form
`{
app
namespace}
`
.
`
{username}`
. Th
is
makes everything before the first
`.`
namespace where the secret for that
user has to be created and everything after that as the username
.
To
allow
secrets in a different namespace other than the
Postgres cluster
na
mespace
. Once enabled
, specify the namespace in the user name under th
e
`users`
section
in the form
`{namespace}
.
{username}`
. Th
e operator will then
create the user secret in that namespace. The part after the first
`.`
is
considered to be the user name. The default is
`false`
.
*
**enable_init_containers**
global option to allow for creating init containers in the cluster manifest to
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment