Closed slopezz closed 2 years ago
operator-utils was updated to github.com/redhat-cop/operator-utils v1.2.2
at https://github.com/3scale-ops/saas-operator/commit/8618a1afbcbff4007abda5fe80d6363b5f068763
Pending to try to reproduce the issue test documented at https://github.com/3scale-ops/saas-operator/issues/126#issue-1012282475 to verify it is already fixed
We have seen, that with current
redhat-cop/operator-utils:v1.1.3
(based onoperator-sdk v1.3
, the same operatorsdk version used at saas-operator), when removing resources like PDB/HPA, randomly they are not deleted and need to be deleted manually (they are not recreated because the controller no longers reconciles it).It seems the recocile controller to delete it fails, and on next reconcile thinks it is no longer required to watch it.
I have done some changes on backend and system controllers, deploying initially a basic CR:
By default, if not specified, it creates a PDB/HPA for worker and listener:
Then deploy the same CR, but removing their PDB/HPA:
And randomly one PDB and HPA (backend or listener), persists and is not deleted, and need to be manually deleted:
After doing some tests using newer
redhat-cop/operator-utils:v1.1.4
(based onoperator-sdk v1.9
), the issue seems to be fixed, at least I have not been able to reproduce it, so when removing PDB/HPA from CR spec, they are really deleted.