-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Kops update with private networking is trying to change NatGateway #1073
Comments
I don't see a change being made to AWS in the logs? |
^ specifically
Goind to see if the update changes the NatGateway.... |
yah this smells like a bug:
|
Simple steps to recreate:
|
Need to test against We have PR inbound thay may help with this ... I am looking through issues to test against #1183 - no promises but we need to test. |
This should be closed ;) |
Closing this. |
Bug description
Our new integration tests are showing that
kops update
is actually changing aws components. It is my understanding that an update preps the cluster for an update and does not touch aws resources.Steps to recreate
You can recreate by running the
make e2e
target in my PR #1064. You will need the following env vars to run the tests:What the tests actually do
The sequence the test is doing:
Logs from testing
Open question
Not sure if #1072 fixed this, but I am thinking no.
The text was updated successfully, but these errors were encountered: