essobedo commented on issue #3473:
URL: https://github.com/apache/camel-k/issues/3473#issuecomment-1233182839
I confirm that leases (along with integrations, integration kits, builds,
camel catalogs, Kamelet bindings...) are not deleted by the uninstall command
however they don't prevent the install command to work as expected since the
install command only checks whether an integration platform with the same name
already exists in the namespace and the integration platform is properly
removed by the uninstall command.
The lease exists in the namespace...
```
$ kubectl get lease -n foo
NAME HOLDER
AGE
camel-k-lock
camel-k-operator-848fd8785b-7knql_626532a4-c05f-4edb-8cd9-7f6294d6cc57 13m
```
but it doesn't prevent the install command to work as expected
```
kamel install -n foo
OLM is not available in the cluster. Fallback to regular installation.
Warning: the operator won't be able to detect a local image registry via
KEP-1755
Camel K installed in namespace foo
```
Knowing that, shall we still remove the lease on uninstall?
--
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]
