Kubernetes performs soft delete and waits for object hard delete until finalizers == 0. During that period any actions for soft deleted objects aren't performend. It caues weird behavior for service accounts, deployments and etc. When kubernetes-controller manager ignores actions that must be performend with it. For instance, pod creation for soft deleted deployment.
Operator now detects soft delete and free objects. An object ll be recreate at the next reconcile loop and error message ll be logged.
Kubernetes performs soft delete and waits for object hard delete until finalizers == 0. During that period any actions for soft deleted objects aren't performend. It caues weird behavior for service accounts, deployments and etc. When kubernetes-controller manager ignores actions that must be performend with it. For instance, pod creation for soft deleted deployment.
Operator now detects soft delete and free objects. An object ll be recreate at the next reconcile loop and error message ll be logged.
https://github.com/VictoriaMetrics/operator/issues/953