Spinnaker Pipeline is failing after starting it manually

8/6/2019

Spinnaker on Gke :

Pipeline is getting failed after starting manually

the first issue is the .spin/config didnt get created, I created that manually as missing in the steps https://cloud.google.com/solutions/continuous-delivery-spinnaker-kubernetes-engine then when i started pipeline manually , it is giving me an error on production stage

Exception ( Wait For Manifest To Stabilize ) WaitForManifestStableTask of stage Deploy Production Backend timed out after 30 minutes 4 seconds. pausedDuration: 0 seconds, elapsedTime: 30 minutes 4 seconds,timeoutValue: 30 minutes

-- Vidya Sawanny
config
google-kubernetes-engine
spinnaker

2 Answers

8/27/2019

I find this Spinnaker GitHub page insightful. I wanted to add it as a comment because I still don't have enough reputation.

-- Ismail
Source: StackOverflow

8/6/2019

Many times this is caused by Kubernetes being unable to schedule the pods. Just had the same problem this morning and it was due to lack of resources. That would be the first thing I'd check. You can find the pod in the "Server Group" under the "Infrastructure" tab and view the details of why it's in the state it is.

-- John Davis
Source: StackOverflow