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

Bug 2099800: bump to k8s 1.24.6 #1381

Merged
merged 193 commits into from
Oct 11, 2022

Conversation

soltysh
Copy link

@soltysh soltysh commented Oct 4, 2022

Supersedes #1352

soltysh and others added 30 commits April 29, 2022 16:46
A previous commit updated the containerd version used on Windows
nodes from 1.5.4 to 1.6.2. However, the folder structure of the
containerd releases changed since then from:

cni/$binary.exe

to:

cni/bin/$binary.exe

Because of this, the Windows nodes do not have the necessary CNI
binaries needed to setup the pod networks.
Change-Id: Ic231ce9a5504d3aae4191901d7eb5fe69bf017ac
Change-Id: I99206f35f6f145054c005ab362c792e71b9b15f4
In some rare race conditions, the job controller might create new pods after the job is declared finished.

Change-Id: I8a00429c8845463259cd7f82bb3c241d0011583c
Change-Id: Ia6e86da5e66422fdb653c1ee60864a1c79233ea6
During upgrade when a CP node is missing the old / legacy "master"
taint, assume the user has manually removed it to allow
workloads to schedule.

In such cases do not re-taint the node with the new "control-plane"
taint.
SpecAggregator's GetAPIServiceNames method returned empty APIService
name by mistake, causing OpenAPI controller handling an invalid
APIService continuously.

Signed-off-by: Quan Tian <qtian@vmware.com>
…erry-pick-of-#109486-upstream-release-1.24

Automated cherry pick of kubernetes#109486: Integration test for backoff limit and finalizers
…pick-of-#109840-origin-release-1.24

Automated cherry pick of kubernetes#109840: kubeadm: only taint CP nodes when the legacy "master" taint
Make sure that nodes that are not in the ready state and are not newly created (i.e. not having the "node.cloudprovider.kubernetes.io/uninitialized" taint) get removed from load balancers.
Also remove nodes that are being deleted from the cluster.

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
…of-#109836-upstream-release-1.24

Automated cherry pick of kubernetes#109836: Fix OpenAPI loading error caused by empty APIService
Resolved issues with proxy rules taking a long time to be synced on Windows, by caching HNS data.

In particular, the following HNS data will be cached for the context of syncProxyRules:
  * HNS endpoints

  * HNS load balancers
Otherwise the event handler might not be called.

Change-Id: I23c93c2251b411430a0f2469686db6355d84af2f
The cached token authenticator returns a cache value. The group adder changes it.
Signed-off-by: cpanato <ctadeu@gmail.com>
[release-1.24][GO]Update Go to 1.18.2
create (POST) custom resources should be scope:resource
…ick-of-#109880-upstream-release-1.24

Automated cherry pick of kubernetes#109880: Remove warning log for merging meta and scale type
…ick-of-#109858-upstream-release-1.24

Automated cherry pick of kubernetes#109858: GCE: skip updating and deleting external loadbalancers if
…f-#109969-upstream-release-1.24

Automated cherry pick of kubernetes#109969: authn: fix cache mutation by AuthenticatedGroupAdder
…-of-#109928-upstream-release-1.24

Automated cherry pick of kubernetes#109928: Fix ServiceIPStaticSubrange assigns duplicate IP addresses
…erry-pick-of-#109947-upstream-release-1.24

Automated cherry pick of kubernetes#109947: Wait for cache to sync in job's TestWatchOrphanPods
the 1.24 test suite will try to find both old + new taint on the CP nodes, but kubeadm 1.25 will only add the new taint. https://github.com/kubernetes/kubernetes/pull/110095/files#r875034086
@openshift-ci
Copy link

openshift-ci bot commented Oct 10, 2022

@soltysh: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • ci/prow-verify-commits

Only the following failed contexts/checkruns were expected:

  • ci/prow/4.11-upgrade-from-stable-4.10-images
  • ci/prow/artifacts
  • ci/prow/e2e-agnostic-cmd
  • ci/prow/e2e-aws-cgroupsv2
  • ci/prow/e2e-aws-crun
  • ci/prow/e2e-aws-csi
  • ci/prow/e2e-aws-downgrade
  • ci/prow/e2e-aws-fips
  • ci/prow/e2e-aws-serial
  • ci/prow/e2e-aws-upgrade
  • ci/prow/e2e-azure-upgrade
  • ci/prow/e2e-gcp
  • ci/prow/e2e-gcp-upgrade
  • ci/prow/images
  • ci/prow/integration
  • ci/prow/k8s-e2e-conformance-aws
  • ci/prow/k8s-e2e-gcp
  • ci/prow/k8s-e2e-gcp-serial
  • ci/prow/unit
  • ci/prow/verify
  • ci/prow/verify-commits
  • pull-ci-openshift-kubernetes-master-4.11-upgrade-from-stable-4.10-images
  • pull-ci-openshift-kubernetes-master-artifacts
  • pull-ci-openshift-kubernetes-master-e2e-aws-csi
  • pull-ci-openshift-kubernetes-master-e2e-aws-downgrade
  • pull-ci-openshift-kubernetes-master-e2e-aws-serial
  • pull-ci-openshift-kubernetes-master-e2e-aws-upgrade
  • pull-ci-openshift-kubernetes-master-e2e-azure-upgrade
  • pull-ci-openshift-kubernetes-master-e2e-gcp
  • pull-ci-openshift-kubernetes-master-images
  • pull-ci-openshift-kubernetes-master-integration
  • pull-ci-openshift-kubernetes-master-k8s-e2e-conformance-aws
  • pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-serial
  • pull-ci-openshift-kubernetes-master-unit
  • pull-ci-openshift-kubernetes-master-verify
  • pull-ci-openshift-kubernetes-master-verify-commits
  • pull-ci-openshift-kubernetes-release-4.10-e2e-agnostic-cmd
  • pull-ci-openshift-kubernetes-release-4.10-e2e-aws-cgroupsv2
  • pull-ci-openshift-kubernetes-release-4.10-e2e-aws-crun
  • pull-ci-openshift-kubernetes-release-4.10-e2e-aws-fips
  • pull-ci-openshift-kubernetes-release-4.10-e2e-gcp-upgrade
  • pull-ci-openshift-kubernetes-release-4.10-k8s-e2e-gcp
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/override ci/prow-verify-commits
this will never pass on a k8s bump bringing in upstream commits not following our commit naming rules

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.

@soltysh
Copy link
Author

soltysh commented Oct 10, 2022

/override ci/prow/verify-commits
this will never pass on a k8s bump bringing in upstream commits not following our commit naming rules

@openshift-ci
Copy link

openshift-ci bot commented Oct 10, 2022

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/verify-commits

In response to this:

/override ci/prow/verify-commits
this will never pass on a k8s bump bringing in upstream commits not following our commit naming rules

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.

@soltysh
Copy link
Author

soltysh commented Oct 10, 2022

/remove-label backports/unvalidated-commits
/label backports/validated-commits
/label bugzilla/valid-bug
we don't have parent bug for this one, so it's complaining about this issue and I need to manually force it

@openshift-ci openshift-ci bot added backports/validated-commits Indicates that all commits come to merged upstream PRs. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Oct 10, 2022
@soltysh
Copy link
Author

soltysh commented Oct 10, 2022

/remove-label bugzilla/invalid-bug

@openshift-ci openshift-ci bot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Oct 10, 2022
@soltysh
Copy link
Author

soltysh commented Oct 11, 2022

/remove-label backports/unvalidated-commits
/label backports/validated-commits
/remove-label bugzilla/invalid-bug
/label bugzilla/valid-bug
we're merging all at once, so we have to manually force valid-bug on it

@openshift-ci
Copy link

openshift-ci bot commented Oct 11, 2022

@soltysh: Those labels are not set on the issue: backports/unvalidated-commits, bugzilla/invalid-bug

In response to this:

/remove-label backports/unvalidated-commits
/label backports/validated-commits
/remove-label bugzilla/invalid-bug
/label bugzilla/valid-bug
we're merging all at once, so we have to manually force valid-bug on it

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.

@tkashem
Copy link

tkashem commented Oct 11, 2022

/lgtm
Thanks!

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 11, 2022
@tkashem
Copy link

tkashem commented Oct 11, 2022

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 11, 2022
@openshift-ci
Copy link

openshift-ci bot commented Oct 11, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: soltysh, tkashem

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

@gangwgr
Copy link

gangwgr commented Oct 11, 2022

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 11, 2022
@openshift-merge-robot openshift-merge-robot merged commit 5157800 into openshift:release-4.11 Oct 11, 2022
@openshift-ci
Copy link

openshift-ci bot commented Oct 11, 2022

@soltysh: All pull requests linked via external trackers have merged:

Bugzilla bug 2099800 has been moved to the MODIFIED state.

In response to this:

Bug 2099800: bump to k8s 1.24.6

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. backports/validated-commits Indicates that all commits come to merged upstream PRs. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.