Bug 1946540 - auth operator: only configure webhook authenticators for internal auth when oauth-apiserver pods are ready
Summary: auth operator: only configure webhook authenticators for internal auth when o...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: apiserver-auth
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Standa Laznicka
QA Contact: liyao
Depends On:
TreeView+ depends on / blocked
Reported: 2021-04-06 11:28 UTC by Standa Laznicka
Modified: 2021-07-27 22:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-07-27 22:57:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-authentication-operator pull 433 0 None open Bug 1946540: only configure webhook authenticators when oauth-apiservers are ready during upgrade 2021-04-14 14:29:20 UTC
Github openshift cluster-authentication-operator pull 435 0 None open Bug 1946540: fix configuring webhook authenticators on upgrade 2021-04-20 09:09:47 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:58:04 UTC

Description Standa Laznicka 2021-04-06 11:28:26 UTC
Description of problem:
In 4.8, the authentication operator configures authentication.spec.webhookTokenAuthenticator, which in turn causes kube-apiserver to rollout with webhook authentication configured towards the oauth-apiservers. However, during upgrade, the configuration event might precede the oauth-apiservers to be fully rolled out, and so authentication may not work properly.

Make sure the authentication.spec.webhookTokenAuthenticator is not set when there are still some oauth-apiserver replicas that are not ready during an update.

Also make sure that once kube-apiserver observes the webhook authenticators configuration, configuring oauth.spec.tokenConfig.accessTokenInactivityTimeout causes no new kube-apiserver rollouts since this configuration no longer should have any effect on kube-apiserver.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce, Actual results, Expected results:
described above

Comment 1 Stefan Schimanski 2021-04-14 12:33:09 UTC
As discussed in Slack, this is a blocker.

Comment 3 Standa Laznicka 2021-04-20 09:08:44 UTC
moving back to ASSIGNED, the original patch was wrong and would prevent webhook authenticators from being configured

Comment 9 errata-xmlrpc 2021-07-27 22:57:48 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.