Getting Kubectl Exec Format Error

[ibanks]

What steps did you take and what happened:
Hello team. I attempted to deploy the latest stable version of Gatekeeper Version 3.18.2. I downloaded the latest helm chart and attempted to deploy via the helm install command

What did you expect to happen:
I expected a successful deployment and for all of the services to be running.

Anything else you would like to add:
What seems to be happening is that the installation is failing on the update-crds-hook step. I'm getting the following error:

$ oc get all -n gatekeeper-system
Warning: apps.openshift.io/v1 DeploymentConfig is deprecated in v4.14+, unavailable in v4.10000+
NAME READY STATUS RESTARTS AGE
pod/gatekeeper-update-crds-hook-22jb7 0/1 Error 0 12m
pod/gatekeeper-update-crds-hook-5dc8r 0/1 Error 0 11m
pod/gatekeeper-update-crds-hook-m2rfv 0/1 Error 0 12m
pod/gatekeeper-update-crds-hook-mq864 0/1 Error 0 13m

NAME COMPLETIONS DURATION AGE
job.batch/gatekeeper-update-crds-hook 0/1 13m 13m
$ oc logs -n gatekeeper-system gatekeeper-update-crds-hook-5dc8r
Defaulted container "crds-upgrade" out of: crds-upgrade, install-oneagent (init)
exec /kubectl: exec format error

Environment:

• Gatekeeper version: 3.18.2
• Kubernetes version: (use kubectl version): v1.27.15

[JaydipGabani]

@ibanks I tried installing GK with 1.27.16 using helm and I am not facing any issues. Can you provide the full helm install command?
Also we are not testing GK with 1.27 or 1.28, we test latest GK versions up until n-2 kubernetes release, so it would be good to update k8s versions to use latest GK.

[ibanks]

Hello @JaydipGabani Thanks for your prompt reply :-) I found the issue. I was pulling the wrong architecture from your image registry. The system that we are running our container orchestration platform on is linux/amd64 (x86_64) architecture. I was accidentally pulling linux/arm64.

I have now successfully deployed the newest stable version of Gatekeeper running on Kubernetes v1.27.15.

I see that you mention that you have not tested Gatekeeper 3.18.2 with this specific version of Kubernetes. Do you think that there is a possibility that Gatekeeper 3.18.2 still works with this Kubernetes version? Unfortunately, we don't have the option at the moment of upgrading to Kubernetes to support Gatekeeper 3.18.2.

[JaydipGabani]

It should work as expected with 1.27 as well since we are pretty mindful of not introduce any breaking changes. However, the latest features such as VAP integration might not work due to lack of ValidatingAdmissionPolicy API in 1.27.

[ibanks]

@JaydipGabani Do you think Gatekeeper 3.18.2 would work with Kubernetes version 1.25?

[JaydipGabani]

It should except VAP, but better stress test it according to your use case before deploying anything in production.