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
The environment variable CLOUD_PROVIDER_API_KEY is present by default in the chart with a Kubecost-provided, hard-coded value. This is to increase user time-to-value and provide less work for them. However, this goes against basic security practices and as a result is being flagged and alerted on by various linters and scanners in CI. Defining sensitive information such as passwords, keys, and API tokens, even if deemed "safe" for public consumption, should be avoided.
Solution Description
Eliminate the hard-coded CLOUD_PROVIDER_API_KEY value and template allowing users to bring their own. Provide documentation instructing users on how to create a key with the required permissions.
Alternatives
No response
Additional Context
No response
Troubleshooting
I have read and followed the issue guidelines and this is a feature request only for the Helm chart.
I have searched other issues in this repository and mine is not recorded.
The text was updated successfully, but these errors were encountered:
Problem Statement
The environment variable
CLOUD_PROVIDER_API_KEY
is present by default in the chart with a Kubecost-provided, hard-coded value. This is to increase user time-to-value and provide less work for them. However, this goes against basic security practices and as a result is being flagged and alerted on by various linters and scanners in CI. Defining sensitive information such as passwords, keys, and API tokens, even if deemed "safe" for public consumption, should be avoided.Solution Description
Eliminate the hard-coded
CLOUD_PROVIDER_API_KEY
value and template allowing users to bring their own. Provide documentation instructing users on how to create a key with the required permissions.Alternatives
No response
Additional Context
No response
Troubleshooting
The text was updated successfully, but these errors were encountered: