[GitHub] [camel-k] christophd commented on issue #4277: Camel-k install and uninstall on a fresh kind cluster in Linux

["christophd (via GitHub)" <gi...@apache.org>]

christophd commented on issue #4277:
URL: https://github.com/apache/camel-k/issues/4277#issuecomment-1522851647

   `kamel uninstall` removes the Camel K resources such as operator deployment, config maps, IntegrationPlatform and so on. But it keeps the cluster wide Camel K resources such as custom resource definitions, service accounts, roles and so on.
   
   `kamel uninstall --all` removes all resources including CRDs and roles
   
   The messages printed during uninstall like `Camel K Integration Platform removed from namespace default` are just informational and do not state the number of actually removed resources for instance.
   
   What's the purpose of calling `uninstall` multiple times?
   
   `KEP-1755` is a mechanism to detect the local registry on a cluster, see [KEP-1755](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/generic/1755-communicating-a-local-registry)
   
   The warning message `the operator won't be able to detect a local image registry via KEP-1755` indicates that the operator was not able to install the required roles that enable access to the KEP-1755 local registry hosting config maps.
   
   In general this will not harm the Camel K functionality. Instead of using KEP-1755 mechanism Camel K will fallback to arbitrary local registry lookup.


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org