Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

camel-k-operator pod CrashLoopBackOff on minikube on restart #537

Closed
stevef1uk opened this issue Mar 7, 2019 · 1 comment
Closed

camel-k-operator pod CrashLoopBackOff on minikube on restart #537

stevef1uk opened this issue Mar 7, 2019 · 1 comment

Comments

@stevef1uk
Copy link
Contributor

stevef1uk commented Mar 7, 2019

Successfully deployed Camel-K on minkube following latest instructions.
Deployed the sample app ok.

minikube stop followed by minishift start using the install instructions command:

minikube start -p camelk --extra-config=apiserver.enable-admission-plugins="LimitRanger,NamespaceExists,NamespaceLifecycle,ResourceQuota,ServiceAccount,DefaultStorageClass,MutatingAdmissionWebhook"

When restarting minikube I see the following error:
camel-k-operator-8d44d99dd-5rxw4 0/1 CrashLoopBackOff 5 7h57m

kubectl logs camel-k-operator-8d44d99dd-5rxw4
{"level":"info","ts":1551982088.6482077,"logger":"cmd","msg":"Go Version: go1.10"}
{"level":"info","ts":1551982088.648258,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":1551982088.6482704,"logger":"cmd","msg":"operator-sdk Version: v0.5.0"}
{"level":"info","ts":1551982088.6483965,"logger":"leader","msg":"Trying to become the leader."}
{"level":"error","ts":1551982118.649228,"logger":"cmd","msg":"","error":"Get https://10.96.0.1:443/api?timeout=32s: dial tcp 10.96.0.1:443: i/o timeout","stacktrace":"github.com/apache/camel-k/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/vendor/github.com/go-logr/zapr/zapr.go:128\nmain.main\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/cmd/manager/main.go:80\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:198"}

My guess is that thus Pod saved the ClusterIP & this has changed on the restart?


My set-up:
minikube version: v0.32.0
Camel K Client 0.3.0

kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-03-01T23:34:27Z", GoVersion:"go1.12", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.0", GitCommit:"0ed33881dc4355495f623c6f22e7dd0b7632b7c0", GitTreeState:"clean", BuildDate:"2018-09-27T16:55:41Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

kubectl cluster-info
Kubernetes master is running at https://192.168.64.32:8443
KubeDNS is running at https://192.168.64.32:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
camel-k-operator ClusterIP 10.108.244.45 60000/TCP 8h
kubernetes ClusterIP 10.96.0.1 443/TCP 8h

@stevef1uk
Copy link
Contributor Author

Resolves itself if left (tried on Camel K Client 0.3.2).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant