From de4ccd51ec0483f82fc73c8ddead788395665d1f Mon Sep 17 00:00:00 2001 From: Praveen Kumar Date: Fri, 22 Nov 2019 11:24:01 +0530 Subject: [PATCH] Issue #131 Tag cluster-kube-apiserver-operator image We need the image to recover the cert in case it expire, if we don't tag it properly then we need to do it on the CRC side and that require the internet connectivity to fetch the hash for KAO image. Now we can directly use `openshift/cert-recovery` tag without fetching it from the release payload. --- createdisk.sh | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/createdisk.sh b/createdisk.sh index b57b3be9..f53581ca 100755 --- a/createdisk.sh +++ b/createdisk.sh @@ -255,6 +255,10 @@ ${OC} --config $1/auth/kubeconfig create secret generic htpass-secret --from-lit ${OC} --config $1/auth/kubeconfig apply -f htpasswd_cr.yaml ${OC} --config $1/auth/kubeconfig create clusterrolebinding developer --clusterrole=sudoer --user=developer +# Get cluster-kube-apiserver-operator image along with hash and tag it +certImage=$(${OC} --config $1/auth/kubeconfig adm release info --image-for=cluster-kube-apiserver-operator) +${SSH} core@api.${CRC_VM_NAME}.${BASE_DOMAIN} -- sudo podman tag $certImage openshift/cert-recovery + # Replace pull secret with a null json string '{}' ${OC} --config $1/auth/kubeconfig replace -f pull-secret.yaml