If the HelmInstance spec changes, all the resources get re-rendered which means some of them may become obsolete (i.e. if some resources are moved from cluster to namespace scope) hence a sort of "garbage collector task" must be executed.
As today, the GC logic would take into account only the resource generation, however, when the operator is updated, the geeneration won't change hence a new algorithm should be implemented to take into account also the release version.
If the
HelmInstance
spec changes, all the resources get re-rendered which means some of them may become obsolete (i.e. if some resources are moved from cluster to namespace scope) hence a sort of "garbage collector task" must be executed.As today, the GC logic would take into account only the resource generation, however, when the operator is updated, the geeneration won't change hence a new algorithm should be implemented to take into account also the release version.
Requires https://github.com/dapr/kubernetes-operator/pull/209