Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Spinnaker uses way too much CPU #3962
There are 7 kubectl context -o json for all resources of the cluster using 100% CPU each (running on vSphere), this causes the spinnaker VM to use 1/3th of an esxi node.
Kubernetes V2 Provider
Localdebian, spinnaker v1.12.1. halyard 1.15, kubernetes 1.13.0
Not sure which microservice is running the kubectl contexts for output.
I'm using account provider v1 & v2, each cluster has a v1 and v2 account configured.
Steps to Reproduce:
Just run the Spinnaker service as usual with a hal deploy apply.
This also happened on our distributed environment, migrating it back to the virtual machine has identified the issue. Spinnaker pods on Kubernetes cluster would crash after 40-48 hours.