Updating openshift-enterprise-hyperkube images to be consistent with ART

[openshift-bot]

Updating openshift-enterprise-hyperkube images to be consistent with ART
TLDR:
Component owners, please ensure that this PR merges as it impacts the fidelity
of your CI signal. Patch-manager / leads, this PR is a no-op from a product
perspective -- feel free to manually apply any labels (e.g. bugzilla/valid-bug) to help the
PR merge as long as tests are passing. If the PR is labeled "needs-ok-to-test", this is
to limit costs for re-testing these PRs while they wait for review. Issue /ok-to-test
to remove this tag and help the PR to merge.

Detail:
This repository is out of sync with the downstream product builds for this component.
One or more images differ from those being used by ART to create product builds. This
should be addressed to ensure that the component's CI testing is accurately
reflecting what customers will experience.

The information within the following ART component metadata is driving this alignment
request: openshift-enterprise-hyperkube.yml.

The vast majority of these PRs are opened because a different Golang version is being
used to build the downstream component. ART compiles most components with the version
of Golang being used by the control plane for a given OpenShift release. Exceptions
to this convention (i.e. you believe your component must be compiled with a Golang
version independent from the control plane) must be granted by the OpenShift
architecture team and communicated to the ART team.

Roles & Responsibilities:

• Component owners are responsible for ensuring these alignment PRs merge with passing
  tests OR that necessary metadata changes are reported to the ART team: @release-artists
  in #aos-art on Slack. If necessary, the changes required by this pull request can be
  introduced with a separate PR opened by the component team. Once the repository is aligned,
  this PR will be closed automatically.
• Patch-manager or those with sufficient privileges within this repository may add
  any required labels to ensure the PR merges once tests are passing. Downstream builds
  are already being built with these changes. Merging this PR only improves the fidelity
  of our CI.

ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image).
In order for your upstream .ci-operator.yaml configuration to be honored, you must set the following in your openshift/release ci-operator configuration file:

build_root:
  from_repository: true

If you have any questions about this pull request, please reach out to @art-team in the #aos-art coreos slack channel.

[openshift-ci-robot]

@openshift-bot: 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:

• bcf7fad|UPSTREAM: : Updating openshift-enterprise-hyperkube images to be consistent with ART: does not specify an upstream backport in the commit message

[openshift-ci-robot]

@openshift-bot: 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:

• bcf7fad|UPSTREAM: : Updating openshift-enterprise-hyperkube images to be consistent with ART: does not specify an upstream backport in the commit message

[openshift-ci-robot]

@openshift-bot: the contents of this pull request could not be automatically validated.

The following commits are valid:

• 046538f|UPSTREAM: 105352: revert pie build mode: the upstream PR kubernetes/kubernetes#105352 has merged
• 279ea00|UPSTREAM: 105462: Do not sync Waiting statuses for Terminated pods: the upstream PR kubernetes/kubernetes#105462 has merged
• 2c140b5|UPSTREAM: 105462: Fix bugs in e2e pod test: the upstream PR kubernetes/kubernetes#105462 has merged
• 320dfcb|UPSTREAM: 105527: Add e2e test to verify kubelet restart behaviour: the upstream PR kubernetes/kubernetes#105527 has merged
• 54cff16|UPSTREAM: 105527: kubelet: set terminated podWorker status for terminated pods: the upstream PR kubernetes/kubernetes#105527 has merged
• 646a425|UPSTREAM: 104582: Remove Error Message Check Dynamic PV Tests: the upstream PR kubernetes/kubernetes#104582 has merged
• 66a5682|UPSTREAM: 105612: Remove Error Message Check Dynamic PV Tests: the upstream PR kubernetes/kubernetes#105612 has merged
• 66e62bc|UPSTREAM: 104847: Handle UID reuse in pod worker: the upstream PR kubernetes/kubernetes#104847 has merged
• 95252e0|UPSTREAM: 104865: e2e iperf2 change threshold to 10MBps = 80 Mbps: the upstream PR kubernetes/kubernetes#104865 has merged
• 970487e|UPSTREAM: 105527: go fmt: the upstream PR kubernetes/kubernetes#105527 has merged
• bee2ceb|UPSTREAM: 105462: Ensure terminal pods maintain terminal status: the upstream PR kubernetes/kubernetes#105462 has merged
• da14fe8|UPSTREAM: 105069: etcd-client starts retrying transient errors from the etcd cluster: the upstream PR kubernetes/kubernetes#105069 has merged

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

• 00cc883|Merge pull request #959 from p0lyn0mial/etcd-client-retry: does not specify an upstream backport in the commit message
• 1b2affc|Merge pull request #1022 from dgrisonnet/bug-2002759: does not specify an upstream backport in the commit message
• 2b79d49|UPSTREAM: : openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc.: does not specify an upstream backport in the commit message
• 3244e4b|UPSTREAM: : update rebase doc: does not specify an upstream backport in the commit message
• 36e8c3c|UPSTREAM: : allow SCC to be disabled on a per-namespace basis: does not specify an upstream backport in the commit message
• 3f9d8b3|UPSTREAM: : update list of deprecated apis: does not specify an upstream backport in the commit message
• 4341263|UPSTREAM: : Updating openshift-enterprise-hyperkube images to be consistent with ART: does not specify an upstream backport in the commit message
• 4d7e196|Merge pull request #1008 from s-urbaniak/force-standard-sccs: does not specify an upstream backport in the commit message
• 54aa574|UPSTREAM: : bump apiserver-library-go: does not specify an upstream backport in the commit message
• 66a3293|UPSTREAM: : bump(apiserver-library-go): does not specify an upstream backport in the commit message
• 674f31e|Merge pull request #1017 from s-urbaniak/bump-scc: does not specify an upstream backport in the commit message
• 726f3aa|Merge pull request #1031 from soltysh/art_version: does not specify an upstream backport in the commit message
• 78fe376|UPSTREAM: : bump(github.com/openshift/apiserver-library-go): Update imagepolicy to support DeploymentConfigs, StatefulSets, and CronJobs: does not specify an upstream backport in the commit message
• 86b82e1|Merge pull request #999 from ehashman/backport-105462: does not specify an upstream backport in the commit message
• 89e406d|Merge pull request #965 from sanchezl/deprecated: does not specify an upstream backport in the commit message
• 91b30ca|Merge pull request #971 from atiratree/bz1965368: does not specify an upstream backport in the commit message
• 9312243|Merge pull request #1007 from rphillips/fixes/filter_terminated_pods_openshift: does not specify an upstream backport in the commit message
• a24cdad|Merge pull request #938 from rphillips/backports/104847: does not specify an upstream backport in the commit message
• a537f4d|Merge pull request #961 from bertinatto/csi-migration-vsphere-azure-file: does not specify an upstream backport in the commit message
• b2a9cd9|UPSTREAM: : verify required http2 cipher suites: does not specify an upstream backport in the commit message
• b2cf147|UPSTREAM: : bump apiserver-library-go: does not specify an upstream backport in the commit message
• bec7497|Merge pull request #993 from rphillips/backports/105452: does not specify an upstream backport in the commit message
• cb14e9a|Merge pull request #1014 from dmage/image-mutator: does not specify an upstream backport in the commit message
• cf887e8|Merge pull request #984 from deads2k/skip-scc: does not specify an upstream backport in the commit message
• d156476|Merge pull request #905 from iamemilio/negative_volume_test_manilla: does not specify an upstream backport in the commit message
• d2641dd|Merge pull request #963 from wking/declare-machine-os-version: does not specify an upstream backport in the commit message
• d767194|Merge pull request #1011 from iamemilio/pv-fix-1.22-origin: does not specify an upstream backport in the commit message
• da3cc90|UPSTREAM: : add CSI migration feature gates for vSphere and Azure File: does not specify an upstream backport in the commit message
• f181eb2|Merge pull request #980 from stbenjam/iperf2: does not specify an upstream backport in the commit message
• f39a06c|Merge pull request #957 from rphillips/add_control_plane: does not specify an upstream backport in the commit message
• f7ae4c0|UPSTREAM: : add control plane to allow roles: does not specify an upstream backport in the commit message

[soltysh]

/retest

[soltysh]

/lgtm
/approve
/label backports/validated-commits
/remove-label backports/unvalidated-commits

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-bot, soltysh

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:

• DOWNSTREAM_OWNERS [soltysh]

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

[soltysh]

/retest

[soltysh]

/test e2e-aws-downgrade

[soltysh]

/retest-required

[soltysh]

/test e2e-azure-upgrade

[soltysh]

/override ci/prow/e2e-agnostic-cmd
which is being worked on elsewhere
/test e2e-azure-upgrade

[openshift-ci]

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/e2e-agnostic-cmd

In response to this:

/override ci/prow/e2e-agnostic-cmd
which is being worked on elsewhere
/test e2e-azure-upgrade

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]

/test e2e-azure-upgrade

[soltysh]

/test e2e-azure-upgrade

[soltysh]

/test e2e-azure-upgrade

[soltysh]

/test e2e-azure-upgrade

[soltysh]

/test e2e-azure-upgrade

[soltysh]

/retest-required

[soltysh]

/test k8s-e2e-gcp