-
Notifications
You must be signed in to change notification settings - Fork 748
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
Increase datastore pool at startup #2354
Conversation
b96ef96
to
ea99b53
Compare
4b7ad82
to
08b3b42
Compare
1122fce
to
86b7843
Compare
timeSinceLast := time.Since(c.lastNodeIPPoolAction) | ||
if timeSinceLast <= interval { | ||
// Make an exception if node needs a trunk ENI and one is not currently attached. |
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.
One callout for this change is that, if trunk ENI fails to attach for any VPC RC issues then aws-node keeps running the reconciliation..maybe as an enhancement we should make it like a backoff retry in cases of SGPP..
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
Release testing should cover negative test cases while increasing the DS pool and trunk ENI failed to attach scenarios.
What type of PR is this?
bug
Which issue does this PR fix:
#1724
What does this PR do / Why do we need it:
This PR fixes two issues:
If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:
N/A
Testing done on this change:
Manually verified that when ENIConfigs are missing, node remains in "Not Ready" state as IPAMD returns error. Also verified that when ENIConfigs are present, ENIs are attached during node initialization.
Verified that CNI integration release tests pass. Scheduling GitHub runner as well.
Automation added to e2e:
N/A
Will this PR introduce any new dependencies?:
No
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No, Yes
Does this change require updates to the CNI daemonset config files to work?:
No
Does this PR introduce any user-facing change?:
Yes
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.