Skip to content
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 1 commit into from
Dec 16, 2019

Conversation

liggitt
Copy link
Member

@liggitt liggitt commented Dec 16, 2019

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?:

Fixes an issue with kubelet-reported pod status on deleted/recreated pods.

/sig node
/cc @wongma7

@k8s-ci-robot k8s-ci-robot requested a review from wongma7 December 16, 2019 19:40
@k8s-ci-robot 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
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot 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
@wongma7
Copy link
Contributor

wongma7 commented Dec 16, 2019

/lgtm
Perfect, thank you

@liggitt
Copy link
Member Author

liggitt commented Dec 16, 2019

flake #86318
/retest

@k8s-ci-robot k8s-ci-robot merged commit eee9dee into kubernetes:master Dec 16, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Dec 16, 2019
@liggitt liggitt deleted the patch-uid branch December 17, 2019 14:02
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants