CODEWITHSUNDEEP
kuberneteskubernetes-helm
Moshe Shaham
Moshe Shaham

Reputation: 15984

Helm install time out

Running helm install for my chart gives my time out error. I have no idea why. Running this in a simple aws instance, no firewall or anything like that. I worked previously and suddenly stopped working.

# helm install xxxx-services-1 chart/ --values chart/values.yaml
Error: failed pre-install: timed out waiting for the condition

already tried:

  1. restarting kubernetes
  2. rebooting the machine
  3. kubeadm reset & kubeadm init

Update:

  1. using helm 3

  2. when I run with --debug, these are last lines, and it's stuck there:

    client.go:463: [debug] Watching for changes to Job xxxx-services-1-ingress-nginx-admission-create with timeout of 5m0s

    client.go:491: [debug] Add/Modify event for xxxx-services-1-ingress-nginx-admission-create: ADDED

    client.go:530: [debug] xxxx-services-1-ingress-nginx-admission-create: Jobs active: 0, jobs failed: 0, jobs succeeded: 0 client.go:491: [debug] Add/Modify event for xxxx-services-1-ingress-nginx-admission-create: MODIFIED

    client.go:530: [debug] xxxxx-services-1-ingress-nginx-admission-create: Jobs active: 1, jobs failed: 0, jobs succeeded: 0

  3. when i do kubectl get jobs i did see an active job, i deleted it, ran the install again - still same result

Upvotes: 0

Views: 16588

Answers (2)

Chris Halcrow
Chris Halcrow

Reputation: 31990

For this type of issue, you may have a pod that's failing to start correctly. Use kubectl describe pod [failing_pod_name] to get a clear indication of what's causing the issue. The issue will be given at the bottom of the output of kubectl describe ...

(Also, adding --debug at the end of your helm install command can show some additional detail)

Upvotes: 1

Moshe Shaham
Moshe Shaham

Reputation: 15984

Found the issue, I didn't taint my master node...

kubectl taint nodes --all node-role.kubernetes.io/master-

I can't believe how much time I spent on this little thing...

Upvotes: 3

Related Questions