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
Kubernetes: Unable to Disable/Destroy cluster #866
Comments
I started looking into this today, and found the cause of the funky message: spinnaker/clouddriver#580 (the error handler catching a 403 was converting a string incorrectly). We still can't toggle pod labels for k8s installations on AWS, but I'm reaching out the client library about that next. See the PR for context. |
Filed a bug: fabric8io/kubernetes-client#396 |
Looks like the latest fabric8 api fixes this issue, going to push a clouddriver release in a minute with the changes. Would appreciate if someone else can verify to double check I've replicated this properly. |
Release is here, should be available in ~20 minutes https://github.com/spinnaker/clouddriver/releases/tag/v1.216.0 |
(Not sure why github auto-closed this issue) |
It works for me, now able to delete clusters. Thanks! |
👍 Ran in the same issue last night, and already fixed! Thanks! |
Environment
I am running Spinnaker from the provided AMI and updated packages using apt. The versions I am currently using are as follows:
For Kubernetes, I am running a CoreOS k8s deployment using kube-aws. I have dropped the config file and all certificates under /home/spinnaker/.kube on the Spinnaker host. I have also confirmed that Spinnaker is able to connect to Kubernetes and successfully create pods.
Steps to Reproduce
Additional Details
Disabling/Destroying will fail on the 'Monitor Server Group' step with the following messages in the clouddriver log. The pods will not be cleaned up on the Kubernetes side.
The text was updated successfully, but these errors were encountered: