Jann Fischer

@CodiumAI-Agent /review

Hi @9strands, the GitOps Operator is based on the upstream Argo CD Operator and provides most (if not all) of its functionality. If you have deployed an Ingress controller to...

Hi, the Operator owns the `argocd-cm`. Please use the `extraConfig` field in the `ArgoCD`'s spec, e.g. ``` spec: extraConfig: accounts.image-updater: .... ```

It is not easy to come with a one-size-fits-all recommendation (and that's why we don't deliver resource limits by default), because the requirements vary on a lot of factors. For...

This could be rather easily integrated after we implement https://github.com/argoproj/argo-cd/pull/14964

@dependabot rebase

@dependabot recreate

@dependabot rebase

To prevent this behaviour, you can set the resource tracking method to annotation, as described [here](https://argo-cd.readthedocs.io/en/stable/user-guide/resource_tracking/#additional-tracking-methods-via-an-annotation). You will still see the resources created by Cilium, but Argo CD will not...

I like that approach, @leoluz. It's simple enough to be useful for me. As a con, I'd like to add: Requires some kind of config management tool such as Kustomize...