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

IntegrationPlatform stucked in "status.phase: Starting" #466

Closed
ismailbaskin opened this issue Feb 20, 2019 · 3 comments
Closed

IntegrationPlatform stucked in "status.phase: Starting" #466

ismailbaskin opened this issue Feb 20, 2019 · 3 comments

Comments

@ismailbaskin
Copy link

I'm trying to install camel-k on GKE (1.11.7-gke.6) and followed each step on the documentation. But it does not work. integrationplatform/camel-k stuck in "status.phase: Starting". When investigating camel-k-operator pod logs I've noticed that error.

{
  error:  "Get https://10.241.0.1:443/api?timeout=32s: dial tcp 10.241.0.1:443: connect: connection refused"   
  level:  "error"   
  logger:  "cmd"   
  msg:  ""   
  stacktrace:  "github.com/apache/camel-k/vendor/github.com/go-logr/zapr.(*zapLogger).Error
	/home/lburgazz/work/apache/dev/camel-k-go/src/github.com/apache/camel-k/vendor/github.com/go-logr/zapr/zapr.go:128
main.main
	/home/lburgazz/work/apache/dev/camel-k-go/src/github.com/apache/camel-k/cmd/manager/main.go:80
runtime.main
	/opt/data/sfw/lang/go/1.11.4/src/runtime/proc.go:201"   
  ts:  1550666236.7073588   
 }

After that I've run this command for ensuring and it works as expected.
kubectl exec -it $(kubectl get pod -l name=camel-k-operator -o jsonpath="{.items[0].metadata.name}") -- curl --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt https://10.241.0.1:443/api?timeout=32s

result:

{
  "kind": "APIVersions",
  "versions": [
    "v1"
  ],
  "serverAddressByClientCIDRs": [
    {
      "clientCIDR": "0.0.0.0/0",
      "serverAddress": "XX.XXX.XXX.XXX:443"
    }
  ]
}

Do you have any idea what caused this situation?

@astefanutti
Copy link
Member

Thanks for the report. It seems similar to #431.

@ismailbaskin
Copy link
Author

It is definitely the same error. I've missed that.

@astefanutti
Copy link
Member

Let me close this and follow up in #431.

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

2 participants