How openshift/cluster-authentication-operator works
The cluster-authentication-operator reconciles OpenShift authentication configuration and maintains the OAuth server and OAuth API server operands. An administrator configures cluster authentication; the operator observes configuration, reconciles operand resources and supporting auth features, then evaluates health and reports status. The graph preserves documented capability areas and central controllers. Some controller wiring is supported by the starter's SOURCE INDEX references; unsampled implementation details and relationships are not inferred.
Main entry points: starter.go Operator startup · wellknown_ready_controller.go Well-known readiness · config_observer_controller.go Config observation · deployment_controller.go OAuth server workload
Components 17
Operator control
- Operator startup
pkg/operator/starter.go - Config observation
pkg/operator/configobservation/configobservercontroller/config_observer_controller.go - Payload configuration
pkg/controllers/payload/payload_config_controller.go
OAuth operand
- OAuth server workload
pkg/controllers/deployment/deployment_controller.go - OAuth API workload
pkg/operator/workload/sync_openshift_oauth_apiserver.go - Custom route
pkg/controllers/customroute/custom_route_controller.go - Ingress state
pkg/controllers/ingressstate/ingress_state_controller.go - Proxy configuration
pkg/controllers/proxyconfig/proxyconfig_controller.go - Router certificates
pkg/controllers/routercerts/controller.go
Authentication features
- External OIDC
pkg/controllers/externaloidc/externaloidc_controller.go - Webhook authenticator
pkg/controllers/webhookauthenticator/webhookauthenticator_controller.go - OAuth clients
pkg/controllers/oauthclientscontroller/oauthclientscontroller.go - Legacy OAuth APIs
pkg/operator/legacy_oauth_apis.go
Health and status
- OAuth endpoints
pkg/controllers/oauthendpoints/oauth_endpoints_controller.go - Well-known readiness
pkg/controllers/readiness/wellknown_ready_controller.go - Operator metadata
pkg/controllers/metadata/metadata_controller.go
Other components
- Cluster administrator
Connections 22
- Cluster administrator → Operator startup: configures cluster
- Operator startup → Config observation: starts
pkg/operator/starter.go - Operator startup → Payload configuration: starts
pkg/operator/starter.go - Operator startup → OAuth server workload: starts
pkg/operator/starter.go - Operator startup → OAuth API workload: starts
pkg/operator/starter.go - Operator startup → Custom route: starts
pkg/operator/starter.go - Operator startup → Ingress state: starts
pkg/operator/starter.go - Operator startup → Proxy configuration: starts
pkg/operator/starter.go - Operator startup → Router certificates: starts
pkg/operator/starter.go - Operator startup → External OIDC: starts
pkg/operator/starter.go - Operator startup → Webhook authenticator: starts
pkg/operator/starter.go - Operator startup → OAuth clients: starts
pkg/operator/starter.go - Operator startup → Legacy OAuth APIs: initializes
pkg/operator/starter.go - Operator startup → OAuth endpoints: starts
pkg/operator/starter.go - Operator startup → Well-known readiness: starts
pkg/operator/starter.go - Operator startup → Operator metadata: starts
pkg/operator/starter.go - Config observation → Payload configuration: observes configuration
pkg/controllers/payload/payload_config_controller.go - OAuth server workload → Cluster administrator: serves login
- OAuth API workload → Cluster administrator: serves OAuth API
- Custom route → Ingress state: updates status
pkg/controllers/customroute/custom_route_controller.go - OAuth endpoints → Well-known readiness: checks service health
- Well-known readiness → Operator metadata: reports readiness