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

Helm Chart apiKey field #230

Open
zaphinath opened this issue Aug 22, 2023 · 0 comments
Open

Helm Chart apiKey field #230

zaphinath opened this issue Aug 22, 2023 · 0 comments

Comments

@zaphinath
Copy link

zaphinath commented Aug 22, 2023

In the values file for the helm chart it has the following

# apiKey or secretName is REQUIRED.
# You must generate a template to get your apiKey.
# In the Cloudability app, go to Insights -> Containers, then click
# the provisioning cluster button that will take you through our provisioning workflow.

From reading this I assume if I have the field apiKey filled out that it will just put that directly as the environment variable CLOUDABILITY_API_KEY and not try to pull from a secret - because there is a second field secretName. If I leave secretName blank and add the apiKey it still tries to create the secret and reference that.

I would be happy to make a PR to the template if this functionality sounds right. Ultimately we really don't need to store the api key as a secret and just want to reference it in the deployment (makes our automation easier and it is already secure from the namespace it is in).

A second related question is can the api key be the same for different clusters or does each cluster we have need it's own api key?

Thanks

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

No branches or pull requests

1 participant