k0pper opened a new issue #2702: URL: https://github.com/apache/camel-k/issues/2702
### Error Installing camel-k on a minikube cluster worked completely fine. But on a real cluster (OnPrem) using the `kamel intsall` command gives me this error: `Error: cannot get current namespace: invalid configuration: unable to read certificate-authority certs/k8s-stage/k8s-ca.crt for k8s-stage due to open certs/k8s-stage/k8s-ca.crt: no such file or directory` ### Failed solutions I checked my local certs. The k8s-ca.crt is present. I redownloaded it from the server which hosts the kubernetes cluster: `curl --create-dirs -s http://KUBERNETES-SERVER.com/ca.pem -o ${HOME}/.kube/certs/k8s-stage/k8s-ca.crt` Afterwards, I reconfigured kubectl to use the set certificate and the server ``` kubectl config set-cluster k8s-stage \ --certificate-authority=${HOME}/.kube/certs/k8s-stage/k8s-ca.crt \ --server=https://KUBERNETES-SERVER.com:6443 ``` And still I get the error. As I understood it, I need to give my kubectl client the certificate which is needed to interact with the kubernetes cluster. Strange enough, I can still interact with it and only `kamel` commands give me this error. I can still for instance list pods in the namespace. Any ideas? Is there something I do not understand correctly? -- 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-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
