Open sechmann opened 11 months ago
something to consider is using replicator when creating team resources
Gut reflex says using replicator will just introduce another layer of "things that might go wrong", and added delay before the namespace is ready. We already need to have an authenticated k8s client anywyas, (which we need to create the namespace), why not use it? Might be wrong.
We should make an additional feature that is auto-installed in all tenant clusters This should poll
teams-backend
for updates and make sure the state in each of the tenant clusters is what we expect. Much like thenaisd
integration today.The reason we want to do this is simply because it doesn't fit in in
naisd
. Makes more sense to separate.