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 nodepools section starts at line 3, but it doesn’t handle labels or taints.
The nodepool section, starting at line 122, does include logic for labels and taints, but it doesn’t align with the way the values.yaml file is structured.
Hey @shabazzfsher... thanks for submitting this issue! I will take a look at why we they aren't being applied...
I don't believe the labels/taints/annotations not being applied will have to do with the nodepools vs nodepool You can see they are working as expected due to the code below:
{{- $clustername := .Values.cluster.name -}}
{{- if eq .Values.cloudprovider "amazonec2" }}
{{- range $index, $nodepool := .Values.nodepools }}
AND
{{ $nodepool := .Values.nodepool }}
{{- if$nodepool }}
RGS customer is experiencing an issue with the AWS cluster template in the Rancher Cluster Templates Helm chart (v0.6.1). Labels and taints defined in the values.yaml file are not being applied to clusters as expected. The issue seems to originate in the AWS template file:
https://github.com/rancherfederal/rancher-cluster-templates/blob/rancher-cluster-templates-0.6.1/charts/cluster-templates/templates/nodeconfig-aws.yaml
Additionally, the values-aws.yaml file only includes a nodepools section, with no mention of nodepool:
https://github.com/rancherfederal/rancher-cluster-templates/blob/rancher-cluster-templates-0.6.1/charts/cluster-templates/values-aws.yaml
This discrepancy results in labels and taints being ignored unless they are manually applied or the Helm template is adjusted accordingly.
The text was updated successfully, but these errors were encountered: