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.

Sign up for GitHub

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

Jump to bottom

OCPBUGS-48364: Update to Kubernetes 1.31.4 #2179

Merged
merged 10 commits into from
Jan 24, 2025
Merged

OCPBUGS-48364: Update to Kubernetes 1.31.4 #2179

merged 10 commits into from
Jan 24, 2025

Conversation

bertinatto
Copy link
Member

@bertinatto bertinatto commented Jan 20, 2025 •
edited
Loading

/assign @atiratree

#2163 was created for 4.18, but I miss updating in master as well. This PR is intended to fix that.

adrianmoisey and others added 10 commits November 14, 2024 20:00
@adrianmoisey
Ensure that a node's CIDR isn't released until the node is deleted
ea299ac 
Fixes kubernetes#127792

Fixes bug where a node's PodCIDR was released when the node was given a
delete time stamp, but was hanging around due to a finalizer.
@k8s-release-robot
Update CHANGELOG/CHANGELOG-1.31.md for v1.31.3
953a3a8
@cpanato
Bump images, dependencies and versions to go 1.22.9 and distroless ip…
779a082 
…tables

Signed-off-by: cpanato <[email protected]>
@k8s-ci-robot
Merge pull request kubernetes#128912 from cpanato/update-go-131
d89400f 
[release-1.31][go] Bump images, dependencies and versions to go 1.22.9 and distroless iptables
@k8s-ci-robot
Merge pull request kubernetes#128806 from adrianmoisey/automated-cher…
b73931a 
…ry-pick-of-#128305-upstream-release-1.31

Automated cherry pick of kubernetes#128305: Ensure that a node's CIDR isn't released until the node is deleted
@umagnus @andyzhangx
fix isLikelyNotMountPointStatx relative path issue
80964ef
@k8s-ci-robot
Merge pull request kubernetes#129004 from andyzhangx/automated-cherry…
9968b8d 
…-pick-of-#128286-upstream-release-1.31

Automated cherry pick of kubernetes#128286: fix isLikelyNotMountPointStatx relative path issue
@k8s-release-robot
Release commit for Kubernetes v1.31.4
a78aa47
@bertinatto
Merge tag 'v1.31.4' into bump-1.31.4-master
a004c63 
Kubernetes official release v1.31.4
@bertinatto
UPSTREAM: <drop>: hack/update-vendor.sh, make update and update image
9213bbe
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jan 20, 2025
@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot requested review from deads2k and p0lyn0mial January 20, 2025 13:34
@openshift-ci openshift-ci bot added vendor-update Touching vendor dir or related files approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 20, 2025
@bertinatto bertinatto changed the title Update to Kubernetes 1.31.4 OCPBUGS-48364: Update to Kubernetes 1.31.4 Jan 20, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 20, 2025
@openshift-ci-robot
Copy link

@bertinatto: This pull request references Jira Issue OCPBUGS-48364, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

/assign @atiratree

#2163 was created for 4.18, but I miss updating in master as well. This PR is intended to fix that.

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 openshift-eng/jira-lifecycle-plugin repository.

@atiratree
Copy link
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 20, 2025
@openshift-ci-robot
Copy link

@atiratree: This pull request references Jira Issue OCPBUGS-48364, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from wangke19 January 20, 2025 13:42
@atiratree
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 20, 2025
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jan 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: atiratree, bertinatto

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

@bertinatto
Copy link
Member Author

/remove-label backports/unvalidated-commits
/label backports/validated-commits
/label acknowledge-critical-fixes-only

Trying to bring 4.19 on pair with 4.18.

@openshift-ci openshift-ci bot added backports/validated-commits Indicates that all commits come to merged upstream PRs. acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Jan 20, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b2db1e and 2 for PR HEAD 9213bbe in total

@bertinatto
Copy link
Member Author

/retest-required

1 similar comment
@bertinatto
Copy link
Member Author

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b2db1e and 2 for PR HEAD 9213bbe in total

6 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b2db1e and 2 for PR HEAD 9213bbe in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b2db1e and 2 for PR HEAD 9213bbe in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b2db1e and 2 for PR HEAD 9213bbe in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b2db1e and 2 for PR HEAD 9213bbe in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b2db1e and 2 for PR HEAD 9213bbe in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b2db1e and 2 for PR HEAD 9213bbe in total

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jan 23, 2025 •
edited
Loading

@bertinatto: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 9213bbe link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b2db1e and 2 for PR HEAD 9213bbe in total

@openshift-merge-bot openshift-merge-bot bot merged commit d6d0ba1 into openshift:master Jan 24, 2025
24 of 25 checks passed
@openshift-ci-robot
Copy link

@bertinatto: Jira Issue OCPBUGS-48364: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-48364 has been moved to the MODIFIED state.

In response to this:

/assign @atiratree

#2163 was created for 4.18, but I miss updating in master as well. This PR is intended to fix that.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-pod
This PR has been included in build openshift-enterprise-pod-container-v4.19.0-202501240608.p0.gd6d0ba1.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: kube-proxy
This PR has been included in build kube-proxy-container-v4.19.0-202501240608.p0.gd6d0ba1.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-hyperkube
This PR has been included in build openshift-enterprise-hyperkube-container-v4.19.0-202501240608.p0.gd6d0ba1.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-kube-apiserver-artifacts
This PR has been included in build ose-installer-kube-apiserver-artifacts-container-v4.19.0-202501240608.p0.gd6d0ba1.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@deads2k deads2k Awaiting requested review from deads2k

@p0lyn0mial p0lyn0mial Awaiting requested review from p0lyn0mial

@wangke19 wangke19 Awaiting requested review from wangke19

Assignees

@atiratree atiratree

Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
9 participants
@bertinatto @openshift-ci-robot @atiratree @openshift-bot @adrianmoisey @k8s-release-robot @cpanato @k8s-ci-robot @umagnus