*** Bug 2028615 has been marked as a duplicate of this bug. ***
Verified with cluster-bot cluster with PR 429 (launch 4.8-ci,openshift/cloud-credential-operator#429 aws)
1. Check pod-identity-webhook pod log, no "Error fetching secret"
W1206 06:25:55.569752 1 client_config.go:615] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I1206 06:25:55.573631 1 main.go:191] Creating server
I1206 06:25:55.574435 1 main.go:211] Listening on :9999 for metrics and healthz
I1206 06:25:55.574549 1 main.go:205] Listening on :6443
2. Check creationTimestamp of secret pod-identity-webhook is before that of "Creating server" in log
oc get secret pod-identity-webhook -n openshift-cloud-credential-operator -o yaml
3. Check the volume in pod-identity-webhook yaml
oc get pod pod-identity-webhook-844494b567-qw8kq -n openshift-cloud-credential-operator -o yaml
- name: webhook-certs
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.24 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.