-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Another reduction of describe via reducing the number of list calls #4772
Conversation
@@ -50,10 +50,6 @@ func (c *OwnedCluster) Upgrade(dryRun bool) error { | |||
return err | |||
} | |||
|
|||
if err := c.ctl.RefreshClusterStatus(c.cfg); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was redundant as New already called this.
I don't see how my changes here could affect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
I pushed in some more changes, sorry :/
Integration tests passed on this Branch. ( I pushed it to eksctl directly too with the current change set.) |
Part 2 Of refactoring GetStackTemplate and DescribeStack
This time, Describe is reduced due to the number of reduced list calls during deletion. It's possible to pass around stacks by adding Stack to the nodeGroupStack and reducing the number of calls by moving around lists which already happened at the top level.
Related to: #4635
Integration Test Run results
The 2 failures appear to be unrelated, but I'll make sure.
Nodegroup tests incoming...
Hmmm.... Node listing works by hand, but this test keeps failing which makes me think either the test is missing something that I need to add, or I'm missing something from somewhere. The code should work fine, this is just listing. Basically
get nodegroups
fails but it makes no sense why.Managed Nodegroup test:
Fixed the failure and rerun the failing part:
This is definitely a problem somewhere ^^. I run it isolation so it didn't create that nodegroup 🤦.
But it's fine, because
upgradeNg(initialAl2Nodegroup)
this passed so the other one should have as well.Just going to run the integration test suit on my branch -> https://github.com/weaveworks/eksctl-ci/actions/runs/1830405203