catshout opened a new issue #2533: URL: https://github.com/apache/camel-k/issues/2533
I've installed Camel-K in a namespace "camel-k" in a GCP (Google Cloud Platform) k8s cluster. As next I deployed 1 simple integration [hello.zip](https://github.com/apache/camel-k/files/6886878/hello.zip) in this namespace. I performed the following commands to uninstall and re-install Camel-K ``` kamel uninstall --all --global kubectl config set-context --current --namespace=default kubectl delete namespace camel-k kubectl create namespace camel-k kubectl config set-context --current --namespace=camel-k kubectl create secret generic kaniko-secret --from-file=/home/cas-dev-gke/kaniko-secret.json kamel install --build-publish-strategy=Kaniko --registry gcr.io --organization cas-dev-gke --registry-secret kaniko-secret --global ``` I'd expect that the Camel-K operator will become available but former Integrations in this namespace must be deployed again. As I experienced all Integrations in this namespace Camel-K are automatically deployed after Camel-K re-install. Side note: An uninstall of Camel-K 1.4 und re-install of Camel-K 1.5 leave the Camel-L operator in a deadlock. We did have to remove all Integrations and re-deploy. -- 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]
