9ca87d9db4
When a Postgres cluster has a finalizer, deleting it sets a DeletionTimestamp but doesn't remove the object until the finalizer is cleared. The operator was not properly handling these DeletionTimestamp changes: 1. postgresqlUpdate() was filtering out events where only DeletionTimestamp changed (it only checked Spec and Annotations), causing the delete to never be processed. 2. EventUpdate case in processEvent() didn't check for DeletionTimestamp, so even if the event reached the processor, it would run Update() instead of Delete(). 3. removeFinalizer() used a cached object with stale resourceVersion, causing "object has been modified" errors. Fixes: - Add explicit DeletionTimestamp check in postgresqlUpdate() to queue the event - Add DeletionTimestamp check in EventUpdate to call Delete() when set - Fetch latest object from API before removing finalizer to avoid conflicts |
||
|---|---|---|
| .. | ||
| controller.go | ||
| logs_and_api.go | ||
| node.go | ||
| node_test.go | ||
| operator_config.go | ||
| pod.go | ||
| postgresql.go | ||
| postgresql_test.go | ||
| types.go | ||
| util.go | ||
| util_test.go | ||