[GitHub] [camel-k] catshout opened a new issue #3013: kamel uninstall seems to remain some resources in the cluster

[GitBox <gi...@apache.org>]

catshout opened a new issue #3013:
URL: https://github.com/apache/camel-k/issues/3013


   We do have 2 namespaces
   
   camel-k for the global Camel-K Operator
   integration for integrations
   
   The Camel-K Operator has been installed in global mode in the namespace camel-k.
   
   I did perform the following commands on our k8s cluster to cleanup the Camel-K installation ..
   
   ```
   kamel reset -n camel-k
   kamel reset -n integration
   kamel uninstall --global --all
   kubectl delete ns camel-k
   kubectl delete ns integration
   
   ```
   
   After that I did run ..
   
   ```
   kubectl create ns camel-k
   kubectl config set-context $(kubectl config current-context) --namespace camel-k
   kubectl create secret generic kaniko-secret --from-file=/home/cas-dev-gke/kaniko-secret.json -n camel-k
   kamel install --global --build-publish-strategy=Kaniko --registry gcr.io --organization cas-dev-gke --registry-secret kaniko-secret -n camel-k
   ```
   
   I got a message so far ..
   
   ```
   Error: Camel K seems already installed (use the --force option to overwrite existing resources): integrationplatforms.camel.apache.org "camel-k" already exists
   ```
   
   It seems that something remains even after the Operator uninstall and namespace deletion.


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

[GitHub] [camel-k] squakez commented on issue #3013: kamel uninstall seems to remain some resources in the cluster

[GitBox <gi...@apache.org>]

squakez commented on issue #3013:
URL: https://github.com/apache/camel-k/issues/3013#issuecomment-1043021080


   I've tried the scenario a few times and sometimes it works correctly, but sometimes it fails (for me it failed with a pending service-account resource). In theory, the removal procedure is taking care of all resources:
   ```
   $ kamel uninstall --global --all
   Camel K Integration Platform removed from namespace default
   Camel K Config Maps removed from namespace default
   Camel K Registry Secret removed from namespace default
   Camel K platform Kamelets removed from namespace default
   Camel K Operator removed from namespace default
   Camel K Role Bindings removed from namespace default
   Camel K Roles removed from namespace default
   Camel K Service Accounts removed from namespace default
   Camel K Custom Resource Definitions removed from cluster
   Camel K Cluster Role Bindings removed from cluster
   Camel K Cluster Roles removed from cluster
   ```
   For the time being, you please use the `--force` option to overcome the problem.


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