-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
unable to change zones of control plane #8817
Comments
/assign |
Can you have a look at the linked PR and see if this works for you? |
How do I test this, do I just |
If you can build a kops client from that PR and just do this how you expect to do this, it would be good. You can ping me on slack if you need any direct assistance. Hopefully the validation logic should guide you. I'll stress again that when it comes to deleting master IGs you need to take care yourself not to break quorum (i.e you can only delete less than half of the master IGs at the same time). If you break quorum you may have to restore etcd from backup. |
1. What
kops
version are you running? The commandkops version
, will displaythis information.
1.13
2. What Kubernetes version are you running?
kubectl version
will print theversion if a cluster is running or provide the Kubernetes version specified as
a
kops
flag.1.13
3. What cloud provider are you using?
aws
4. What commands did you run? What is the simplest way to reproduce this issue?
Create cluster:
Change cluster zones:
5. What happened after the commands executed?
The terraform apply gets stuck waiting for the etcd volumes to get destroyed.
I tried manually terminating the EC2 instances using these volumes.
This allowe a second try of change steps 2-4 to succeed but kops validate no longer validates so not possible to do a kops rolling-update.
6. What did you expect to happen?
I expected the terraform apply to complete successfully and then the rolling-update to be possible and successful.
7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml
to display your cluster manifest.You may want to remove your cluster name and other sensitive information.
8. Please run the commands with most verbose logging by adding the
-v 10
flag.Paste the logs into this report, or in a gist and provide the gist link here.
9. Anything else do we need to know?
The text was updated successfully, but these errors were encountered: