-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Add UID precondition to kubelet pod status patch updates #86320
Merged
Merged
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
k8s-ci-robot
added
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
kind/bug
Categorizes issue or PR as related to a bug.
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
kind/flake
Categorizes issue or PR as related to a flaky test.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
labels
Dec 16, 2019
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt 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 |
k8s-ci-robot
added
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
area/kubelet
labels
Dec 16, 2019
/lgtm |
k8s-ci-robot
added
the
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
label
Dec 16, 2019
This was referenced Dec 16, 2019
Merged
flake #86318 |
k8s-ci-robot
added a commit
that referenced
this pull request
Dec 25, 2019
…0-upstream-release-1.16 Automated cherry pick of #86320: Add UID precondition to kubelet pod status patch updates
k8s-ci-robot
added a commit
that referenced
this pull request
Dec 25, 2019
…0-upstream-release-1.17 [v1.17.1] Automated cherry pick of #86320: Add UID precondition to kubelet pod status patch updates
k8s-ci-robot
added a commit
that referenced
this pull request
Dec 25, 2019
…0-upstream-release-1.15 Automated cherry pick of #86320: Add UID precondition to kubelet pod status patch updates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
area/kubelet
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
kind/bug
Categorizes issue or PR as related to a bug.
kind/flake
Categorizes issue or PR as related to a flaky test.
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
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?
/kind bug
/kind flake
What this PR does / why we need it:
When patching pod status, kubelets should ensure their patch only applies to the same instance of the pod they observed. Otherwise, the kubelet can associate an incorrect resulting resource version with a deleted/replaced pod (e.g. a statefulset pod).
Which issue(s) this PR fixes:
xref #82387 (comment)
Does this PR introduce a user-facing change?:
/sig node
/cc @wongma7