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

Store api-path as a ConfigMap #1843

Open
samayer12 opened this issue Feb 18, 2025 · 0 comments
Open

Store api-path as a ConfigMap #1843

samayer12 opened this issue Feb 18, 2025 · 0 comments

Comments

@samayer12
Copy link
Contributor

Describe what should be investigated or refactored

api-path is stored as a K8s secret, but does not contain sensitive information. Therefore, we should store it as a ConfigMap.

We'll know this refactor is complete when we do not have a secret in a deployed cluster that contains the value of api-token.

From the docs:

Secrets are similar to ConfigMaps but are specifically intended to hold confidential data.

and

ConfigMap does not provide secrecy or encryption. If the data you want to store are confidential, use a Secret rather than a ConfigMap, or use additional (third party) tools to keep your data private.

Links to any relevant code

N/A

Additional context

Related PR discussion in #1830

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant