astefanutti commented on issue #3311:
URL: https://github.com/apache/camel-k/issues/3311#issuecomment-1141741093

   > I did a simple test that created a new project (namespace) and then 
installed an operator and ran a few integrations 
(`examples/languages/{Sample.java,simple.js,routes.yaml}`) in it. After they 
were up I deleted the project without cleaning up any Camel K resources and all 
the resources were wiped out with the deleted project. So we already have the 
behaviour we expect.
   > 
   > If the namespace deletion is stuck, then probably there are some problems 
with the finalizers for some remaining resources. You can force deleting those 
resources like this:
   > 
   > ```
   > kubectl patch ... --type=merge -p '{"metadata": {"finalizers":null}}'
   > ```
   > 
   > but I think it should be specific to the settings of some tests and we 
should investigate why the finalizer for the resource is stuck in the tests.
   
   +1, namespaced resources, such as integrations, are deleted by the GC 
controller when their namespace is deleted. The problem, as outlined by 
@tadayosi, is that some namespaces are still pending deletion, e.g.: 
   
   ```
   test-b0a72b56-3909-43f4-8a65-43f47127f68e | Terminating | Process of being 
deleted
   ```
   
   Finalizers set on resources within the namespace may be a possible cause.


-- 
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]

Reply via email to