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
While setting up k8s-monitoring using the onboarding docs, I encountered the following error when running terraform apply:
│ Error: execution error at (k8s-monitoring/templates/validations.yaml:1:4):
│ The Helm chart values appears to be from version 1.x of the k8s-monitoring Helm chart.
│ To continue using version 1.x, add this to your helm command:
│ --version ^1
│
│ If you'd like to migrate to version 2.0, see the Migration guide:
│ https://github.com/grafana/k8s-monitoring-helm/blob/main/charts/k8s-monitoring/docs/Migration.md
│
│ with helm_release.grafana-k8s-monitoring,
│ on grafana-k8s-monitoring.tf line 1, in resource "helm_release" "grafana-k8s-monitoring":
│ 1: resource "helm_release" "grafana-k8s-monitoring" {
│
Steps to Reproduce
Follow the instructions in linked onboarding docs to install the k8s-monitoring Helm chart.
Run terraform apply.
Encounter the version mismatch error above.
Suggested Fix
Option 1: Update the documentation to include version = "1.6.23" in the helm_release resource so that people don't hit this error.
Option 2: Change the documentation to explain setting up v2.
Congrats on the release!
The text was updated successfully, but these errors were encountered:
bensenescu
changed the title
Helm Chart Version Conflict in Documentation
Onboarding Docs Error - Not updated to V2, but terraform points to v2 by default
Jan 31, 2025
Description
While setting up k8s-monitoring using the onboarding docs, I encountered the following error when running
terraform apply
:Steps to Reproduce
terraform apply
.Suggested Fix
Option 1: Update the documentation to include version = "1.6.23" in the helm_release resource so that people don't hit this error.
Option 2: Change the documentation to explain setting up v2.
Congrats on the release!
The text was updated successfully, but these errors were encountered: