Open otaviof opened 7 years ago
We ran into the same problem, we end up using --disable delete
all over the place.
We include the environment in our prefix, but that is getting unwieldy. Another solution is to use a separate tiller namespace per environment, we are planning to move to this because we can also keep the configmaps and tiller rbac separate.
Considering that we have two namespaces, one
test
and anotheracceptance
, and a release namednginx
with prefixprereq
is being deployed on both environments. My expected outcome would be that both namespaces would getprereq-nginx
installed, but what happens is that it get removed from the first namespace (what is not the target of Landscaper's current run).On debugging logging we can observe:
At
state_provider.go
+271 we have:So it only filters by the regexp applied on prefix, on which the example here it matches on two different namespaces, then would be possible to exclude releases that are not currently on target namespace? I think the desired behavior is to only "delete" the release if it's deployed on the same (target) namespace, and on this example both
prereq-nginx
would be kept.