UPSTREAM: <drop>: bump openshift, k8s to 1.22.1

[wking]

Asking to merge #950 back into 4.9, effectively making it as if the master/4.9 fork had happened a bit later than it actually did.

[openshift-ci]

@wking: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

UPSTREAM: : bump openshift, k8s to 1.22.1

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.

[openshift-ci-robot]

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

The following commits are valid:

• 4d8071e|UPSTREAM: 104817: kubelet: Rejected pods should be filtered from admission: the upstream PR kubernetes/kubernetes#104817 has merged
• f60a6d3|UPSTREAM: 104314: legacy-cloud-providers: aws: Add support for consuming web identity credentials: the upstream PR kubernetes/kubernetes#104314 has merged

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

• 43892aa|Merge pull request #927 from sjenning/pick-104314: does not specify an upstream backport in the commit message
• 5c24c72|Merge pull request #893 from deads2k/etcd-health-carry: does not specify an upstream backport in the commit message
• 7f39387|UPSTREAM: : 104437: run etcd healthcheck in the background and reply with a cached value: does not specify an upstream backport in the commit message
• da66296|Merge pull request #948 from rphillips/backports/104817: does not specify an upstream backport in the commit message
• ebd3f49|UPSTREAM: : bump openshift, k8s to 1.22.1: does not specify an upstream backport in the commit message

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wking
To complete the pull request process, please assign soltysh after the PR has been reviewed.
You can assign the PR to them by writing /assign @soltysh in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@wking: 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:

• 0a3a771|UPSTREAM: : bump openshift, k8s to 1.22.1: does not specify an upstream backport in the commit message

[wking]

#950's ebd3f49 had merge conflicts in pkg/kubelet/kubelet_pods.go. ebd3f49 -> 0a3a771 takes us from "use the #950 commit directly" to "cherry pick that commit (and not the other stuff that landed right before #950) on top of release-4.9".

[openshift-ci]

@wking: The following tests 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/k8s-e2e-gcp	0a3a771	link	true	/test k8s-e2e-gcp
ci/prow/e2e-openstack-csi-manila	0a3a771	link	false	/test e2e-openstack-csi-manila
ci/prow/e2e-openstack-csi-cinder	0a3a771	link	false	/test e2e-openstack-csi-cinder
ci/prow/e2e-agnostic-cmd	0a3a771	link	false	/test e2e-agnostic-cmd
ci/prow/k8s-e2e-aws-serial	0a3a771	link	true	/test k8s-e2e-aws-serial

Full PR test history. Your PR dashboard.

Details

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

[sttts]

/hold

We cannot do this. It switches over dependencies to 4.10 versions.

[wking]

/close

[openshift-ci]

@wking: Closed this PR.

Details

In response to this:

/close

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.