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

[openshift-bot]

Updating openshift-enterprise-pod 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-pod.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:

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

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

[wking]

/bugzilla refresh

[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.

Retaining the bugzilla/valid-bug label as it was manually added.

In response to this:

/bugzilla 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 kubernetes/test-infra repository.

[openshift-ci-robot]

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

The following commits are valid:

• 01a8b05|UPSTREAM: 108366: test: Add E2E for job completions with cpu reservation: the upstream PR kubernetes/kubernetes#108366 has merged
• 0f44280|UPSTREAM: 107847: service REST: Call Decorator(old) on update path: the upstream PR kubernetes/kubernetes#107847 has merged
• 15270f8|UPSTREAM: 107900: kubelet: Clean up a static pod that has been terminated before starting: the upstream PR kubernetes/kubernetes#107900 has merged
• 34e46fd|UPSTREAM: 108366: test: Verify that nodes do not transition to Failed while ready: the upstream PR kubernetes/kubernetes#108366 has merged
• 363dfdc|UPSTREAM: 109283: test/e2e/*: default existing tests to privileged pod security policy: the upstream PR kubernetes/kubernetes#109283 has merged
• 379eab7|UPSTREAM: 108366: test: Add E2E for init container pod deletion: the upstream PR kubernetes/kubernetes#108366 has merged
• 383840f|UPSTREAM: 109487: Disable JobTrackingWithFinalizers due to unresolved bug: the upstream PR kubernetes/kubernetes#109487 has merged
• 4bf9a12|UPSTREAM: 106454: test/e2e: fix e2e tests for restricted policy: the upstream PR kubernetes/kubernetes#106454 has merged
• 542e1f8|UPSTREAM: 106454: SQUASH: test/e2e/framework: add pod security admission configuration: the upstream PR kubernetes/kubernetes#106454 has merged
• a59fd94|UPSTREAM: 108284: fix: exclude non-ready nodes and deleted nodes from azure load balancers: the upstream PR kubernetes/kubernetes#108284 has merged
• b6288ea|UPSTREAM: 106454: test/e2e: fix e2e tests for restricted policy: the upstream PR kubernetes/kubernetes#106454 has merged
• bde35ea|UPSTREAM: 107831: Include pod UID in secret/configmap cache key: the upstream PR kubernetes/kubernetes#107831 has merged
• cf60012|UPSTREAM: 106454: test/e2e: fix e2e tests for restricted policy: the upstream PR kubernetes/kubernetes#106454 has merged
• d99a317|UPSTREAM: 108149: fix: do not return early in the node informer when there is no change of the topology label.: the upstream PR kubernetes/kubernetes#108149 has merged
• db4c4bb|UPSTREAM: 107900: Add an e2e test for updating a static pod while it restarts: the upstream PR kubernetes/kubernetes#107900 has merged
• edaf80f|UPSTREAM: 107786: Ensure the execHostnameTest() compares hostnames: the upstream PR kubernetes/kubernetes#107786 has merged
• eee5c5e|UPSTREAM: 107821: Move kubelet secret and configmap manager calls to sync_Pod functions: the upstream PR kubernetes/kubernetes#107821 has merged
• f9aead4|UPSTREAM: 108366: kubelet: Delay writing a terminal phase until the pod is terminated: the upstream PR kubernetes/kubernetes#108366 has merged

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

• 0233338|Merge pull request #1210 from ravisantoshgudimetla/patch-1: does not specify an upstream backport in the commit message
• 02aefbf|Merge pull request #1199 from rphillips/backport/107845_108366: does not specify an upstream backport in the commit message
• 0568d29|Merge pull request #1156 from aojea/dual_begin_update: does not specify an upstream backport in the commit message
• 0c3aeba|UPSTREAM: : update list of deprecated apis: does not specify an upstream backport in the commit message
• 194b639|Merge pull request #1184 from ricky-rav/dev_az_node_informer_upstream_master: does not specify an upstream backport in the commit message
• 21cef0d|Merge pull request #1215 from tkashem/rest-mappings: does not specify an upstream backport in the commit message
• 2a2851c|Merge pull request #1226 from s-urbaniak/fix-e2e-tests: does not specify an upstream backport in the commit message
• 3219acd|Merge pull request #977 from pixelsoccupied/master: does not specify an upstream backport in the commit message
• 32ce0d0|UPSTREAM: : enable e2e test after 1.23 rebase in sdn: does not specify an upstream backport in the commit message
• 37c5e75|Merge pull request #1230 from jsafrane/skip-azure-topology: does not specify an upstream backport in the commit message
• 3f7f68a|UPSTREAM: : enable should drop INVALID conntrack entries test: does not specify an upstream backport in the commit message
• 4062053|Merge pull request #1238 from s-urbaniak/existing-tests-privileged: does not specify an upstream backport in the commit message
• 42a86de|Merge pull request #1153 from shiftstack/bug2044824: does not specify an upstream backport in the commit message
• 476a929|Merge pull request #1176 from harche/bug_2040533: does not specify an upstream backport in the commit message
• 54654d2|Merge pull request #1110 from atiratree/console-redirect: does not specify an upstream backport in the commit message
• 58f3815|UPSTREAM: : use hardcoded rest mapper from library-go: does not specify an upstream backport in the commit message
• 5b8b08c|UPSTREAM: : apirequestcount filter should skip non-resources: does not specify an upstream backport in the commit message
• 5fbf419|UPSTREAM: : apirequestcount validation: does not specify an upstream backport in the commit message
• 64ce37d|Merge pull request #1204 from sanchezl/patch-2: does not specify an upstream backport in the commit message
• 65ef2f4|Merge pull request #1128 from s-urbaniak/psa-e2e-backport: does not specify an upstream backport in the commit message
• 67e1c1d|UPSTREAM: : Remove pod warning annotation when workload partitioning is disabled: does not specify an upstream backport in the commit message
• 69213f8|Merge pull request #1251 from ravisantoshgudimetla/increase-loglevel: does not specify an upstream backport in the commit message
• 6f15ddb|UPSTREAM: : Bug 2062459: Generate event when cache update is failed: does not specify an upstream backport in the commit message
• 7447f79|UPSTREAM: : Ignore container notfound error while getPodstatuses: does not specify an upstream backport in the commit message
• 7478cf2|Merge pull request #1190 from ricky-rav/dev_2040715_nodestatus: does not specify an upstream backport in the commit message
• 7871e95|UPSTREAM: : Skip in-tree topology tests win Azure Disk migrated to CSI: does not specify an upstream backport in the commit message
• 78ebfce|Merge pull request #897 from jluhrsen/bz-1945329: does not specify an upstream backport in the commit message
• 801ac6f|UPSTREAM: : zero-diff to pick up tags for versions: does not specify an upstream backport in the commit message
• 95ee4b2|Merge pull request #1228 from danwinship/re-disable-sdn-networkpolicy: does not specify an upstream backport in the commit message
• 96a18e0|UPSTREAM: : update e2es: does not specify an upstream backport in the commit message
• a8f15f6|UPSTREAM: : Generate event when cache update failed: does not specify an upstream backport in the commit message
• aba8d20|UPSTREAM: : Unskip OCP SDN related tests: does not specify an upstream backport in the commit message
• b085777|Merge pull request #1212 from s-urbaniak/fix-e2e-tests: does not specify an upstream backport in the commit message
• b99c800|UPSTREAM: : bump(apiserver-library-go): inclusion of seccompProfile fields in SCC admission: does not specify an upstream backport in the commit message
• c77caa8|UPSTREAM: : update vendor files: does not specify an upstream backport in the commit message
• d032c6e|UPSTREAM: revert: : Unskip OCP SDN related tests: does not specify an upstream backport in the commit message
• d36f9d8|Merge pull request #1172 from sanchezl/apirequestcounts-panic: does not specify an upstream backport in the commit message
• d464c70|Merge pull request #1243 from soltysh/bug2075621: does not specify an upstream backport in the commit message
• d67dd91|Merge pull request #1201 from astoycos/activate-netpol-sdn: does not specify an upstream backport in the commit message
• d7b268f|UPSTREAM: : use console-public config map for console redirect: does not specify an upstream backport in the commit message
• d9c78a9|UPSTREAM: : Updating openshift-enterprise-pod images to be consistent with ART: does not specify an upstream backport in the commit message
• e23f142|UPSTREAM: : ignore invalid apirequestcounts: does not specify an upstream backport in the commit message
• e7218b0|Merge pull request #1225 from rphillips/backports/108756: does not specify an upstream backport in the commit message
• eccb385|Merge pull request #1227 from s-urbaniak/e2e-fixes: does not specify an upstream backport in the commit message
• f017760|Merge pull request #1197 from ricky-rav/dev_bz_2034958bis: does not specify an upstream backport in the commit message
• f14faf2|Merge pull request #1157 from rphillips/test_107854: does not specify an upstream backport in the commit message
• f2bf203|Merge pull request #1218 from stlaz/seccomp_ga_sync: does not specify an upstream backport in the commit message
• fe7796f|Merge pull request #1193 from deads2k/zero-diff-4.11: does not specify an upstream backport in the commit message

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

[openshift-ci]

@openshift-bot: 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/e2e-aws-cgroupsv2	d9c78a9	link	false	/test e2e-aws-cgroupsv2
ci/prow/e2e-gcp-upgrade	d9c78a9	link	true	/test e2e-gcp-upgrade
ci/prow/images	d9c78a9	link	true	/test images
ci/prow/e2e-aws-serial	d9c78a9	link	true	/test e2e-aws-serial
ci/prow/e2e-aws-fips	d9c78a9	link	true	/test e2e-aws-fips
ci/prow/k8s-e2e-gcp-serial	d9c78a9	link	true	/test k8s-e2e-gcp-serial
ci/prow/k8s-e2e-conformance-aws	d9c78a9	link	true	/test k8s-e2e-conformance-aws
ci/prow/e2e-gcp	d9c78a9	link	true	/test e2e-gcp
ci/prow/e2e-aws-crun	d9c78a9	link	true	/test e2e-aws-crun
ci/prow/e2e-aws-csi	d9c78a9	link	false	/test e2e-aws-csi
ci/prow/verify	d9c78a9	link	true	/test verify
ci/prow/e2e-agnostic-cmd	d9c78a9	link	false	/test e2e-agnostic-cmd
ci/prow/k8s-e2e-gcp	d9c78a9	link	true	/test k8s-e2e-gcp

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