You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: