phantomjinx opened a new issue, #3311: URL: https://github.com/apache/camel-k/issues/3311
When running the e2e tests, I found that despite the namespaces being deleted after each test, the integrations, integrationKits and integrationPlatforms are not. Leaving a cluster for some time leads to an accumulation of these resources and the performance of a global operator degrades since on starting up, it first has to reconcile all of these resources currently installed but not necessarily 'visible' (due to their namespace having been deleted). `$ kubectl get namespaces | grep test` test-618a87b4-b8fb-496e-adbf-90510372faa6 | Active | Left over from testing test-b0a72b56-3909-43f4-8a65-43f47127f68e | Terminating | Process of being deleted test-d37b5d1c-c9d1-4360-b731-aa5b6c76ce6f | Terminating | Process of being deleted `$ kubectl get integrationplatforms --all-namespaces` | NAMESPACE | NAME | PHASE | | ------------------- | -------- | ---------- | | openshift-operators | camel-k | Ready | Only 'valid' integrationplatform that should still be around | test-3c9e5d26-67a0-46da-9118-40415180fd1b | secondary | Ready | Should have been delected by now | test-97103a00-4a22-4ddd-b28b-4769d59c2f52 | camel-k | Ready | Should be being deleted by terminating namespace ```oc get integrationkits --all-namespaces``` | NAMESPACE | NAME | PHASE | TYPE | IMAGE | ------------------- | -------- | ---------- | ---------- | ---------- | | test-97103a00-4a22-4ddd-b28b-4769d59c2f52 | kit-ca8hkn95ggpi4b4o0gbg | Ready | platform | image-registry.openshift-image-registry.svc:5000/test-97103a00-4a22-4ddd-b28b-4769d59c2f52/camel-k-kit-[.....]4fa8a3 | test-97103a00-4a22-4ddd-b28b-4769d59c2f52 | kit-ca8hm0idkk603440sajg | Ready | platform | image-registry.openshift-image-registry.svc:5000/test-97103a00-4a22-4ddd-b28b-4769d59c2f52/camel-k-kit-[.....]dc7b21 Both should have been deleted by terminating namespace? ```oc get integrations --all-namespaces```` | NAMESPACE | NAME | PHASE | KIT | REPLICAS | ------------------- | -------- | ---------- | ---------- | ---------- | test-02610ee1-f79e-4456-a8bc-0c9c42816575 | display | Building Kit | test-02d27e76-90b8-4413-ae18-f4d87384d3cc | yaml | Building Kit | test-08581fd1-d69f-468e-a782-52efb74797b9 | yaml | Building Kit | test-0a6f7e5e-bbbf-4bc6-be5d-d9a22064bd5b | service-binding | Running | kit-c921mmhj5m71rdvhut60 | 1 test-123faa08-1d51-4ecb-b4d1-1d6ea4e605f7 | first | Running | kit-c7orcon7vfna3ammv0ug | 1 test-123faa08-1d51-4ecb-b4d1-1d6ea4e605f7 | second | Running | kit-c7orcon7vfna3ammv0ug | 1 test-1a27e89f-5994-4a14-9d05-e7fd0c209925 | yaml | Building Kit | test-1e86a177-e143-489b-8db8-9b62000cc195 | petstore | Running | kit-c93nje5iadjqhe238cv0 | 0 test-1e97efd0-b18d-47de-9048-38b5cb8f82e3 | podtest-knative1 | Running | kit-c7grdq79fpis8lk5k250 | 1 test-1e97efd0-b18d-47de-9048-38b5cb8f82e3 | podtest-knative2 | Running | kit-c7grcuf9fpis8lk5k24g | 1 test-28c56377-e4f4-4362-8f63-c03e8349a124 | first | Running | kit-c7o73e2tqbcb2nde0vag | 1 test-28c56377-e4f4-4362-8f63-c03e8349a124 | second | Running | kit-c7o73e2tqbcb2nde0vag | 1 ..... | ..... 50+ more | ...... | I notice that none of these resouces have the `owner` property assigning them either to the operator or to the namespace. Perhaps, adding this will ensure that deleting either the operator or namespace (depending on which is chosen) will then remove them. Question is whether to attach them to the operator or to the namespace? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
