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
{{ message }}
This repository has been archived by the owner on Jul 15, 2024. It is now read-only.
2 very straightforward questions about ArgoCD ApplicationSet manifests:
When shipping a new ApplicationSet manifest, is the intended use supposed to be kubectl apply or kubectl create?
IF an existing ApplicationSet spec changes -- specifically if we change spec.generators.git.revision - for that existing AppSet...are we supposed to run kubectl apply or kubectl update or kubectl replace?
Thank you for any help or guidance. I have read the documentation for k8s and what the difference is between each of these commands from a high level, but I am trying to understand how these choices practically affect our GitOps workflow.
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
-
2 very straightforward questions about ArgoCD ApplicationSet manifests:
When shipping a new ApplicationSet manifest, is the intended use supposed to be
kubectl apply
orkubectl create
?IF an existing ApplicationSet spec changes -- specifically if we change spec.generators.git.revision - for that existing AppSet...are we supposed to run
kubectl apply
orkubectl update
orkubectl replace
?Thank you for any help or guidance. I have read the documentation for k8s and what the difference is between each of these commands from a high level, but I am trying to understand how these choices practically affect our GitOps workflow.
Beta Was this translation helpful? Give feedback.
All reactions