-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.15.0
-
None
-
No
-
False
-
Description of problem:
Per the cert-manager operator guide(https://github.com/openshift/cert-manager-operator/blob/master/README.md) to make and deploy the image on non-x86 arch, pod "cert-manager-operator-controller-manager" will keep CrashLoopBackOff and never be ready.
Version-Release number of selected component (if applicable):
How reproducible:
Build image on non-x86 arch platform like macOS
Steps to Reproduce:
1. Preparing the environment
$ export CONTAINER_ENGINE=docker
$ export REGISTRY=quay.io
$ export REPOSITORY=rh-ee-yuewu
$ export IMAGE_VERSION=1.13-e2e
$ ${CONTAINER_ENGINE} login ${REGISTRY} -u ${REPOSITORY}
$ export IMG=${REGISTRY}/${REPOSITORY}/cert-manager-operator:${IMAGE_VERSION}
2. Build and push the Operator image to a registry
$ make image-build image-push
3. Run the following command to deploy the Cert Manager Operator
$ make deploy
$ oc get po -n cert-manager-operator
Actual results:
$ oc get po -n cert-manager-operator NAME READY STATUS RESTARTS AGE cert-manager-operator-controller-manager-5999fb9b54-qpjvf 1/2 CrashLoopBackOff 3 (42s ago) 85s
Expected results:
$ oc get po -n cert-manager-operator NAME READY STATUS RESTARTS AGE cert-manager-operator-controller-manager-6bd86d85c7-nrn56 2/2 Running 0 9s
Additional info:
Slack threads link: https://redhat-internal.slack.com/archives/C045YMPKR3M/p1699256289043759. Decide to update the readme with the commands for macOS/arm64, like "docker buildx build --platform linux/amd64 ...".
