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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
