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. jira/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 @release-artists 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:

• b619645|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
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Kubernetes Code Review Process.

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

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

• 0f23833|Merge pull request #1537 from tkashem/carry-shutdown-annotation: does not specify an upstream backport in the commit message
• 1399bb6|UPSTREAM: : Move k8s-specific rules to our fork: does not specify an upstream backport in the commit message
• 3f4df4e|UPSTREAM: 117242: CVE-2023-27561: Bump runc go module v1.1.4 -> v1.1.5: the upstream PR kubernetes/kubernetes#117242 has not yet merged
• 59b45a2|UPSTREAM: : Updating openshift-enterprise-pod images to be consistent with ART: does not specify an upstream backport in the commit message
• 6040b96|UPSTREAM: : Change annotation mechanics to allow injecting testMaps and filter out tests: does not specify an upstream backport in the commit message
• 6d90b32|UPSTREAM: 117242: vendor: bump runc to 1.1.6: the upstream PR kubernetes/kubernetes#117242 has not yet merged
• 7185262|UPSTREAM: : add shutdown annotation to response header: does not specify an upstream backport in the commit message
• 80813e6|UPSTREAM: 117310: kube-aggregator: correctly use client-go TLS cache with custom dialer: the upstream PR kubernetes/kubernetes#117310 has not yet merged
• bda0cb5|Merge pull request #1485 from soltysh/test_poc: does not specify an upstream backport in the commit message
• d2e245f|Merge pull request #1548 from benluddy/ocpbugs-10829: does not specify an upstream backport in the commit message
• da9903e|Merge pull request #1518 from haircommander/cpu-load-balance-disable: does not specify an upstream backport in the commit message
• e3df01c|UPSTREAM: : Create minimal wrapper needed to run k8s e2e tests: does not specify an upstream backport in the commit message
• f7b7abc|UPSTREAM: : Update generated: does not specify an upstream backport in the commit message
• fa81b46|UPSTREAM: : disable load balancing on created cgroups when managed is enabled: 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-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:

• 4ddbe4f|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-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:

• 114ba5d|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]

@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/unit	114ba5d	link	true	/test unit
ci/prow/4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade	114ba5d	link	false	/test 4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-serial	114ba5d	link	true	/test e2e-aws-ovn-serial

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.