+++ This bug was initially created as a clone of Bug #2058673 +++ +++ This bug was initially created as a clone of Bug #2058672 +++ +++ This bug was initially created as a clone of Bug #2058671 +++ Description of problem: A number of changes related to the ip-reconciler ( need to be properly implemented, these include: Impact: Without the proper backoff and replacement policies, many failed jobs can build up. Additionally without hostnetworking and use of the api-int lb network connectivity problems which cause errors. Note: A set of changes to the ip-reconciler itself Fixes to include in this (and subsequent backports) include: * auto clean failed jobs (https://github.com/openshift/cluster-network-operator/pull/1318) * Use host network and api-int (https://github.com/openshift/cluster-network-operator/pull/1302) * Disable retries on failure (https://github.com/openshift/cluster-network-operator/pull/1290)
Ran the following to verify this BZ: oc get cronjob ip-reconciler -o yaml -n openshift-multus | grep -Pi "KUBERNETES_SERVICE_PORT|KUBERNETES_SERVICE_HOST|failedJobsHistoryLimit|backoffLimit|hostNetwork" Got output: failedJobsHistoryLimit: 1 backoffLimit: 0 - name: KUBERNETES_SERVICE_PORT - name: KUBERNETES_SERVICE_HOST hostNetwork: true Marking this bug as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.41 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:2272