-
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
Check actual EbsOptimized status during cluster update #3314
Check actual EbsOptimized status during cluster update #3314
Conversation
Hi @Pharb. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/assign @justinsb |
@Pharb not really something that is unit tested easily. I assume that you have run your own e2e tests locally. /ok-to-test |
Yes, I did test this change with my own cluster on AWS and can confirm that this fixes the problem described in #3313 for me. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Pharb, chrislovecnm The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
Nice fix - thank you @Pharb |
/retest |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
Fixes #3313.
It seems like the actual EbsOptimized state of the LaunchConfiguration is not read during
kops update cluster
and always trigges a modification of instance-groups that haverootVolumeOptimization: true
.If any meaningful test can be created for this, please let me know.