*** Bug 2042175 has been marked as a duplicate of this bug. ***
This is upstream fix which is now merged. Marking it 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 (OpenShift Container Platform 4.8.34 bug fix 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.
*** Bug 2039205 has been marked as a duplicate of this bug. ***
Now that 4.8.34 has a public errata, 4.8.25 -> 4.8.34 updates are recommended in fast-4.8:
$ CHANNEL=fast-4.8 hack/available-updates.sh 4.8.25 | tail -n1
4.8.34 quay.io/openshift-release-dev/ocp-release@sha256:016a1e055bc839623abb4d4808f4135ee37b97dcf5b5cf4a586519450e6acbc8 https://access.redhat.com/errata/RHBA-2022:0795
fast-4.8 is fully supported . In the absence of an UpgradeBlocker bug turning up , the update recommendation will appear in stable-4.8 after a delay for collecting and processing feedback .
*** Bug 2040680 has been marked as a duplicate of this bug. ***
*** Bug 2040931 has been marked as a duplicate of this bug. ***
There is another upstream Kubernetes/Kubelet memory leak found and is being tracked by
If a customer is affected by symptoms of kubelet memory leak even after applying fix for this BZ, it is worth checking-out the above BZ. With the help of pprof collected, there is a way to confirm the cause of the leak.
If you do confirm that your customer is affected by the new BZ, please move the case the above BZ. There is no plan to reopen this BZ as the underlying leak is fixed and new leaks need separate tracking.