Version: 4.8.0-fc.7 The <clusterdeployment name>-admin-kubeconfig secret doesn't get created until the spoke cluster is successfully deployed. Ths makes it harder to debug issues during deployment Steps to reproduce: attempt to deploy a spoke cluster with AI/operator. Try to retrieve the secret with kubeconfig: oc get secret `oc get cd -o custom-columns=:.metadata.name`-admin-kubeconfig -o json|jq -r ".data.kubeconfig"|base64 -d result: Error from server (NotFound): secrets "<clusterdeployment>-admin-kubeconfig" not found Expected result: we should get the secret sooner in order to debug possible issues.
Need to upload the secret twice, once when the installation stars, that will upload the kubeconfig without ingress CA and once again when the installation finish.
I'm still seeing this issue with: HUB: 4.8.0-0.nightly-2021-06-23-045512 quay.io/acm-d/acm-custom-registry:2.3.0-DOWNSTREAM-2021-06-22-17-34-59 SPOKE: 4.8.0-fc.9 Which version should I look for?
Hi, this is the master bug. You should look at https://bugzilla.redhat.com/show_bug.cgi?id=1970395
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.9.0 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. https://access.redhat.com/errata/RHSA-2021:3759