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
Automated cherry pick of #61069: Use pod UID as cache key instead of namespace/name #63995
Automated cherry pick of #61069: Use pod UID as cache key instead of namespace/name #63995
Conversation
Per discussion: #61069 (comment) /assign @bsalamat for PR review and approve |
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.
Thanks, @resouer! Looks good. Please make sure the tests pass.
/sig scheduling |
[MILESTONENOTIFIER] Milestone Pull Request: Up-to-date for process @bsalamat @resouer @smarterclayton Pull Request Labels
|
3930989
to
260ea27
Compare
UID uniquely identifies pods across lifecycles, while namespace/name could be 2 different pods across lifecycles. This could result in tricky scheduler bugs. Fixes kubernetes#60966
260ea27
to
880e0cc
Compare
/test pull-kubernetes-e2e-gce |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bsalamat, resouer 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 |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
Cherry pick of #61069 on release-1.9.
#61069: Use pod UID as cache key instead of namespace/name