leotomas837
leotomas837
Any news on this ? @rishabh625 you matrix solution does not work, explanation below. The typical directory structure for this issue is: one config file per cluster and one directory...
After checking, the merge generator is the solution to this problem. Simply set the cluster generator as parent, and the git generator as (only) child, merging on `server` for example...
@brentvatne Any news from it? The workaround suggested in #16084 does not work for managed workflows.
Any news on this ? It has been 7 months...
@Aaron199 Did you make the alert manager service headless ? i.e. `ClusterIP: None`. I suspect that this is due to how the routing algorithm of `ClusterIP` services works (you could...
@wallrj Instructions added
@wallrj Did you get the chance to have a look on this ? I should be straight forward. Let me know if you need anything else from me.
Any update about this ? We are experiencing the same issue. It may be a duplicate from [this issue](https://github.com/argoproj/argo-cd/issues/8663). There is enough RAM, CPU, disk space, and we tried multiplying...
I can make a pull request for this purpose, but can you confirm that the repo is actively monitored and that the PR will be reviewed ?
@raffaelespazzoli any news about this ? It basically highlights that the patch-operator service account (`controller-manager`) does not have the permissions. And indeed, the `serviceAccountRef` does not reference the patch-operator service...