Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feature Request] Enable Copying/Annotation of Generated Secrets to Additional Namespaces #1522

Closed
marcolongol opened this issue Apr 11, 2024 · 4 comments · May be fixed by #1582
Closed

[Feature Request] Enable Copying/Annotation of Generated Secrets to Additional Namespaces #1522

marcolongol opened this issue Apr 11, 2024 · 4 comments · May be fixed by #1582
Labels
stale

Comments

@marcolongol
Copy link

Issue Summary:
Currently, the secrets generated by the CRD are limited to the namespace where the CRD is deployed. It would be beneficial to enable the copying of these secrets to additional namespaces for increased flexibility and usability.

Proposed Solution:
To enable this functionality, additional secret annotations could be exposed in the CRD or inherited from the CRD/StatefulSet. This would allow reflector, replicator or any other annotation-based secret/configMap operator to copy the generated secrets to the specified target namespaces. This enhancement would not only benefit randomly generated passwordSecretRef secrets as discussed in #1323 but also generated connectionStringSecretName secrets.

I'm willing to contribute to this feature by submitting a PR. I would appreciate guidance on the specific files needing modification to implement this functionality.

This feature would greatly improve the usability of the CRD and enhance its flexibility in various deployment scenarios.
@github-actions GitHub Actions
Copy link
Contributor

This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.

@github-actions github-actions bot added the stale label Jun 11, 2024
@limwa limwa mentioned this issue Jul 5, 2024
Open
4 tasks
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Sep 4, 2024

This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.

@github-actions github-actions bot added the stale label Sep 4, 2024
@fealebenpae fealebenpae removed the stale label Sep 23, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.

@github-actions github-actions bot added the stale label Nov 23, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: customize connection string secret annotations limwa/mongodb-kubernetes-operator
3 participants
@fealebenpae @mircea-cosbuc @marcolongol