Hey all! I have a question about best practice that someone might have run into before: We have several Git repos containing

fleet.yaml

files. Each one of those has several corresponding

GitRepo

s in Continuous Delivery each one pointing at different clusters. This lets us change a branch on a

GitRepo

pointing to a sandbox cluster so we can POC changes without affecting production. Once the branch gets merged to

main

branch the changes are propagated to all clusters that reference the

main

branch. This works really well but it's a huge bottleneck because only one engineer can be referencing that sandbox cluster at a time with their selected development branch. Question: Has anyone else run into this and does anyone have any examples of ways they've solved this in the past? I can't really give everyone their own sandbox cluster yet, unfortunately, or I'd just do that.

I know I've deployed the same GitRepo multiple times but with different paths/targets etc. so I assume you could do this with specified branches too. I think you'd just need to be really careful figuring out the implications on namespaces for your circumstances.

Thanks for the reply @salmon-train-47748! Good call on using namespaces in a single cluster. I'm going to set up a POC to see what kinds of issues I run into there. I know we use abstract (not in the same namespace) tooling like Istio and CertManager that would collide even if the base app is in a unique namespace. Still it's worth a try as long as I don't need FQDNs for my sandbox-level POCs.