Improve startup performance of IPAM by optimizing kube client creation #1855
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
backjo
changed the title
backjo
changed the title
M00nF1sh
approved these changes
Apr 11, 2022
sushrk
pushed a commit
to sushrk/amazon-vpc-cni-k8s
that referenced
this pull request
Jun 17, 2022
aws#1855) * fix: improve startup performance of kube clients * fix: improve startup performance of kube clients * fix: improve startup performance of kube clients * fix: improve startup performance of kube clients * fix compile failure in cni-metrics-helper Co-authored-by: M00nF1sh <yyyng@amazon.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
bug
Which issue does this PR fix:
What does this PR do / Why do we need it:
This improves the startup performance of the IPAM. Right now, when the IPAM initializes, the kube-controller client does API discovery to build a mapper. This operation is done twice (once for the regular client, once for the cache client). This PR re-uses the RESTMapper, and also increases the burst option to reduce client-side throttling happening during the construction of the mapper.
Today, it often takes between 5-10 seconds for these clients to get initialized - see the time difference between k8s cluster communication being validated and the aws session getting started:
If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:
Testing done on this change:
Automation added to e2e:
** Will this PR introduce any new dependencies?**:
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
Does this change require updates to the CNI daemonset config files to work?:
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.