Skip to content

Reference secret in manifestwork instead of putting raw data in it. #46

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
Open
qiujian16 opened this issue Mar 28, 2022 · 2 comments
Open

Reference secret in manifestwork instead of putting raw data in it. #46

qiujian16 opened this issue Mar 28, 2022 · 2 comments
Assignees
@qiujian16

Comments

@qiujian16
Copy link
Member

relating to this issue

open-cluster-management-io/work#114
@qiujian16
Copy link
Member Author

/assign @qiujian16

@bhperry
Copy link
Contributor

bhperry commented Feb 12, 2025

This would be great. The Policy add-on I think partially solves this problem by supporting encrypted values, and I'm guessing if you bind your ManifestWorkReplicaSet and secret Policy to the same Placement then you would get the desired behavior of secret(s) being created for each ManifestWork that is distributed out to spoke clusters.

It would be nice to have support for this in OCM core though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@qiujian16 qiujian16

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@qiujian16 @bhperry