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.

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

feat: store cluster id in a metadata secret #206

Merged
merged 1 commit into from
Dec 5, 2024

Conversation

laimonasr
Copy link
Contributor

No description provided.

return nil
}

secret := &corev1.Secret{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we plan storing any sensitive data here? If not, maybe it would be better to use configMap instead: it is easier to inspect the values with kubectl get cm -o yaml since you don't need to decode the b64.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently there are no plans to store sensitive data and I agree that config map seems like a better store in that case. Cluster id is intended to be used by cluster controller, which currently only supports loading it from a secret and not from a config map that's why I'm storing it in a secret instead

@laimonasr laimonasr force-pushed the store-metadata-in-secret branch 2 times, most recently from 43319a7 to 08bdf35 Compare December 5, 2024 11:55
@laimonasr laimonasr force-pushed the store-metadata-in-secret branch from 08bdf35 to 1f81167 Compare December 5, 2024 12:02
@laimonasr laimonasr merged commit 88447eb into main Dec 5, 2024
2 checks passed
@laimonasr laimonasr deleted the store-metadata-in-secret branch December 5, 2024 12:23
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.

2 participants