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
Imagine that an Argo CD helm application is running on v1.20.11 k8s cluster, and the helm chart contains the following in its template.
{{- $kubeVersion := .Capabilities.KubeVersion.Version }}{{ if semverCompare ">= 1.21.0-0" $kubeVersion }}apiVersion: batch/v1{{ else }}apiVersion: batch/v1beta1{{ end }}kind: CronJob
...
Assuming that I've upgraded the cluster to v1.21.9, would Argo CD recognize the upgrade and re-render the helm chart and sync it so that the new API version is used for the CronJob resource or should I do additional work to upgrade the API version?
I am plannin on k8s version upgrade and want to know the exact behavior of Argo CD.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Imagine that an Argo CD helm application is running on
v1.20.11
k8s cluster, and the helm chart contains the following in its template.Assuming that I've upgraded the cluster to
v1.21.9
, would Argo CD recognize the upgrade and re-render the helm chart and sync it so that the new API version is used for theCronJob
resource or should I do additional work to upgrade the API version?I am plannin on k8s version upgrade and want to know the exact behavior of Argo CD.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions