Skip to content

Copy pod_environment_secret to the cluster namespaces#1789

Closed
dmvolod wants to merge 1 commit into
zalando:masterfrom
dmvolod:issue-1272
Closed

Copy pod_environment_secret to the cluster namespaces#1789
dmvolod wants to merge 1 commit into
zalando:masterfrom
dmvolod:issue-1272

Conversation

@dmvolod

@dmvolod dmvolod commented Feb 21, 2022

Copy link
Copy Markdown
Contributor

Fixes #1272

@FxKu

FxKu commented Mar 1, 2022

Copy link
Copy Markdown
Contributor

The original author of this feature restricted it to the namespace for a reason. Not sure how I should feel about copying a secret with credentials around. @frittentheke fyi.

@dmvolod

dmvolod commented Mar 2, 2022

Copy link
Copy Markdown
Contributor Author

The original author of this feature restricted it to the namespace for a #946 (comment).

Yes, I know, it's a Kubernetes limitations and couldn't be be broken.

Not sure how I should feel about copying a secret with credentials around.

Yes, totally agree with you, for some reasons security restrictions could be occured. But we could introduce an option inside the OperatorConfiguration to copy/not copy secretes form the single location to avoid creation them on every namespace where Postgresql has deployed. Also allowing to configure configmap/secret for each CR (#1794) is more preferred option.

@dmvolod dmvolod closed this Mar 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature request: Copy environment secret to cluster namespaces

2 participants