Replies: 1 comment 5 replies
-
I have seen this type of problem where ArgoCD creates something that, in turn, creates something else. Sometimes, that "something" propagates its labels to its offspring, including the Then Argo looks at that label in the created objects and realizes they are not in the original repo URL and, naturally, decides that these objects are a matter of configuration drift and deletes them. In this scenario, the All that said, I am slightly surprised that the resources are getting recreated, but I guess I would have to see the entire repository to understand the cause for that. Also, if you don't care about managing |
Beta Was this translation helpful? Give feedback.
-
I think i tried everything but i cannot get THe resource to get created and left alone by ArgoCD.
The machineSet im deploying has the keyword CLUSTERID injected in several places of the manifest.
Kyverno will mutate each instance of the word for the actual cluster name.
if i deploy it using
helm install
it works great, but when deployed by ArgoCD it gets created > mutated > Out of Sync > Deleted > created. in an endless loop.i have tried removing all the
jsonPointers
in order to ingore the whole api-resrouce group but even that didn't work.and i'd rather just ignore only the lines that will get mutated by Kyverno, aka anything with CLUSTERID on it.
This is the result of running
helm install kyverno-machineset -f ../../myvalues.yml ./ocp-machineset --dry-run --debug
this is my ArgoCD app.
Beta Was this translation helpful? Give feedback.
All reactions