rumstead

I have been compiling some tunable config here: https://github.com/argoproj/argo-cd/discussions/8446 @todaywasawesome - splitting up Argo CD instances as in running multiple Argo CD UIs or increasing the application controller replicas?

Adding my "bump". EDIT: Use cases: 1. Namespaces/Namespace quotas (cluster bootstrap) 1. Vault (mutating webhook) 1. Service mesh (Consul with a mutating webhook) 1. Capsule (multi-tenancy enabler) 1. Business applications

#323 just to relate them

https://github.com/argoproj-labs/applicationset/issues/61 feels very similar to this.

> What we do in order to configure ArgoCD to work with capsule and capsule-proxy: > > 1. We had a dedicated cluster (we call it management cluster) in each...

Is there a recommendation on how to get the dependencies? ``` sigs.k8s.io/controller-runtime/tools/setup-envtest: module sigs.k8s.io/controller-runtime@latest found (v0.12.3), but does not contain package sigs.k8s.io/controller-runtime/tools/setup-envtest ``` EDIT: Don't love it but it works.....

Can I suggest that we download the envtest tools to [a relative dir](https://github.com/kubernetes-sigs/controller-runtime/blob/bcde6f084dd15ef93bee2a2e4668184e7472eddd/tools/setup-envtest/main.go#L50)? It's clear and obvious where the binaries are downloaded and would get automatically cleaned up if run...

@camilamacedo86 Sorry my comment was unclear. I am actually talking about this line which downloads the k8s binaries to use for the integration tests: https://github.com/kubernetes-sigs/kubebuilder/blob/f2e7a0e214ab4f2bd21b4c3f2ef32eb6f4391445/testdata/project-v4/Makefile#L59 I am using the project-v3...

Looks like metadata.name is also not caught for cronjobs

Happy to contribute time, docs, or code just point me at where to look :).