We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When installing the rancher-monitoring chart via the rancher2_app_v2 resource, values for subcharts are not recognised.
rancher-monitoring
rancher2_app_v2
Terraform Code:
locals { monitoring_chart_values = <<-EOS alertmanager: alertmanagerSpec: storage: volumeClaimTemplate: spec: accessModes: ["ReadWriteOnce"] resources: requests: storage: 10Gi EOS cluster_id = "<CLUSTER_ID>" rancher_monitoring_chart_version = "104.1.0+up57.0.3" } resource "rancher2_app_v2" "rancher_monitoring" { cluster_id = local.rancher_cluster_id name = "rancher-monitoring" namespace = "cattle-monitoring-system" repo_name = "rancher-charts" chart_name = "rancher-monitoring" chart_version = local.rancher_monitoring_chart_version values = local.monitoring_chart_values } output "values" { value = local.monitoring_chart_values }
Deploy the above to a rancher cluster after replacing <CLUSTER_ID> with an actual cluster ID.
<CLUSTER_ID>
Then check the Values YAML in Rancher or Helm to verify the settings are set.
Storage settings are not applied:
alertmanager: alertmanagerSpec: <snip...> storage: {} <snip...>
Values specified for alertmanager are passed through to the alertmanager chart
We originally deployed this instance using the helm_release resource, and later imported it as a rancher2_app_v2
helm_release
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Rancher Server Setup
Information about the Cluster
User Information
Provider Information
Describe the bug
When installing the
rancher-monitoring
chart via therancher2_app_v2
resource, values for subcharts are not recognised.Terraform Code:
To Reproduce
Deploy the above to a rancher cluster after replacing
<CLUSTER_ID>
with an actual cluster ID.Then check the Values YAML in Rancher or Helm to verify the settings are set.
Actual Result
Storage settings are not applied:
Expected Result
Values specified for alertmanager are passed through to the alertmanager chart
Additional Notes
We originally deployed this instance using the
helm_release
resource, and later imported it as arancher2_app_v2
The text was updated successfully, but these errors were encountered: