bump k8s.io/apiserver to 1.20.3:
We need the following cherry pick PRs from upstream (but not limited to):
kube 1.20.3 is going to be released only after the freeze AFAIK, so this can't be done in 4.7
*** This bug has been marked as a duplicate of bug 1917904 ***
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
4.8 dependency is already at 1.21. Setting to MODIFIED for verification and cloned https://bugzilla.redhat.com/show_bug.cgi?id=1965932 for the bump in 4.7.
Note: the bump for 4.8 happened in https://github.com/openshift/oauth-server/commit/be8cde3d7, part of https://github.com/openshift/oauth-server/pull/75
The LifecycleStale keyword was removed because the bug moved to QE and the bug got commented on recently.
The bug assignee was notified.
Like bug 1922646#c11 steps, checked 'oauth-server.*Observed a panic: runtime error: invalid memory address or nil pointer dereference' in 4.8 jobs, no panic found.
> checked 'oauth-server
I made typo. Should use oauth-openshift (i.e. pod name or container name). Double checked again 'oauth-openshift.*bserved a panic: runtime error: invalid memory address or nil pointer', still no issue.
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.2 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.