Skip to content
← Back to activity

Solution skill

Spinnaker on Kubernetes: Not able to start the spinnaker containers in kubernetes

Version 3Sign in to save

Complete solution

Shows how to fix spinnaker on Kubernetes: Not able to start the spinnaker containers in kubernetes. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Based on these errors, it seems that the Front50 service cannot reach any backend(if there is one configured). I would not modify the spinnaker-local.yml file directly, but instead use Halyard to install Spinnaker services into Kubernetes.

Steps

  1. Based on these errors, it seems that the Front50 service cannot reach any backend(if there is one configured). I would not modify the spinnaker-local.yml file directly, but instead use Halyard to install Spinnaker services into Kubernetes. I have setup Spinnaker services in Kubernetes successfully using the instructions and scripts in this repo . Just omit/skip the components that you don't need. https://github.com/grizzthedj/kubernetes-spinnaker

When to use

You are seeing this: I have setup Spinnaker services in Kubernetes successfully using the instructions and scripts in this repo. Use this skill when you run into "Spinnaker on Kubernetes: Not able to start the spinnaker containers in kubernetes".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

  • https://github.com/grizzthedj/kubernetes-spinnaker

Evidence

Source: I was following this documentation to setup Spinnaker on Kubernetes. I ran the scripts as they specified. Then the replication controllers and services are started. But some of PODs are not started root@nveeru~# kubectl get pods --namespace=spinnaker NAME READY STATUS RESTARTS AGE data-redis-master-v000-zsn7e 1/1 Running 0 2h spin-clouddriver-v000-6yr88 1/1 Running 0 47m spin-deck-v000-as4v7 1/1 Running 0 2h spin-echo-v000-g737r 1/1 Running 0 2h spin-front50-v000-v1g6e 0/1 Cr

Verified resolution: Based on these errors, it seems that the Front50 service cannot reach any backend(if there is one configured). I would not modify the spinnaker-local.yml file directly, but instead use Halyard to install Spinnaker services into Kubernetes. I have setup Spinnaker services in Kubernetes successfully using the instructions and scripts in this repo . Just omit/skip the components that you don't need. https://github.com/grizzthedj/kubernetes-spinnaker

Source URL: https://stackoverflow.com/questions/39570765/spinnaker-on-kubernetes-not-able-to-start-the-spinnaker-containers-in-kubernete

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_kpneypb1VKAWRynBC7YTCw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Spinnaker on Kubernetes: Not able to start the spinnaker containers in kubernetes <span>— Vectle</span></a>