-
Notifications
You must be signed in to change notification settings - Fork 38.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
feat: minimize unnecessary API requests to the API server for the configmap/secret get API #120255
feat: minimize unnecessary API requests to the API server for the configmap/secret get API #120255
Conversation
Hi @likakuli. 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 Once the patch is verified, the new status will be reflected by the 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. |
/sig node |
@liggitt kindly ping, please help to review is this ok, thx |
/triage accepted |
65b3cfa
to
f8e1fc8
Compare
…imize unnecessary API requests to the API server for the configmap/secret get API Signed-off-by: likakuli <[email protected]>
f8e1fc8
to
e167ecb
Compare
/ok-to-test |
LGTM label has been added. Git tree hash: 50a11d87a462b1650da9a2c11816d06e95d3df4b
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, likakuli The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #120126
Special notes for your reviewer:
Only invoke AddReference first time when to sync same pod to minimize unnecessary API requests to the API server for the configmap/secret get API.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: