Closed aashishshrestha09 closed 1 month ago
cc @jessegoodier
@aashishshrestha09 I believe this is a warning message which comes from the following code:
To resolve please add the following to your Helm values.
upgrade:
toV2: true
@thomasvn it appears that the template needs to be updated to prevent errors. Since I'm not migrating from v1.x to v2.x, there shouldn't be a need to set upgrade.toV2
to true
in the Helm values.
@aashishshrestha09 Yes, for now the Helm chart expects .Values.upgrade.toV2=true
to be set on all new upgrades. There have been discussions about removing this Helm config in a future release!
Kubecost Helm Chart Version
v2.3.4
Kubernetes Version
1.26
Kubernetes Platform
OpenShift
Description
I'm encountering a ComparisonError when trying to enable RBAC in Kubecost 2.3.4. The error message is:
Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc =
helm template . --name-template kubecost --namespace kubecost --kube-version 1.28 --valuesfailed exit status 1: Error: execution error at (cost-analyzer/templates/NOTES.txt:2:4): SSO with RBAC is enabled. Note that Kubecost 2.x has significant architectural changes that may impact RBAC. This should be tested before giving end-users access to the UI. Kubecost has tested various configurations and believe that 2.x will be 100% compatible with existing configurations. Refer to the following documentation for more information: https://docs.kubecost.com/install-and-configure/install/kubecostv2 When ready to upgrade, add
--set upgrade.toV2=true. Use --debug flag to render out invalid YAML
Note: I have enabled these values in the chart.
Steps to reproduce
Expected behavior
RBAC should be enabled without causing an error.
Impact
This issue prevents us from properly enabling RBAC in Kubecost, which is critical for managing user access and roles. Without RBAC, all authenticated users might have unintended access levels, impacting security and compliance. This prevents us from leveraging Kubecost's full capabilities in a secure and controlled manner.
Screenshots
Logs
Slack discussion
No response
Troubleshooting