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
I believe that this resource marked for pruning is created by some controller, and the tracking label Argo CD uses by default is copied on that resource (also by that controller).
You could either look whether that particular controller could be configured to not copy that label on resources it creates, or you can switch to annotation based resource tracking. Using the latter will give Argo CD more context information on whether a resource is actually managed, or whether labels/annotations were merely copied from another resource.
Checklist:
argocd version
.Describe the bug
Trying to deploy kubescape helm chart with ArgoCD and came across an issue.
ArgoCD prunes a configmap that is part of helm chart deployment.
To Reproduce
Running on k3s v1.27.5+k3s1 (AlpineLinux)
ArgoCD deployment
kubescape deployment
Expected behavior
kubescape installed with helm command works flawlessly
kubescape installed with ArgoCD and same parameters is missing "ks-cloud-config" configmap (https://github.com/kubescape/helm-charts/blob/kubescape-operator-1.15.3/charts/kubescape-operator/templates/configs/cloudapi-configmap.yaml)
Chart source: https://github.com/kubescape/helm-charts/tree/kubescape-operator-1.15.3/charts/kubescape-operator
Screenshots
(ks-cloud-config recreated manually from helm --dry-run --debug)
Version
Logs
Not sure if this is the "interesting" part of log
The text was updated successfully, but these errors were encountered: