no endpoints available for service

[david-wells-1]

I would like to ask for support installing opa gatekeeper v3.21.0 onto a new eks cluster v1.33.

The eks cluster is deployed into private subnets, isolated from the internet. I've updated the image: path in the gatekeeper.yaml file to point to my private image repository and have run the apply command as per instructions and which completes without error.

The pods are not starting, showing error CrashLoopBackOff.

Reviewing CloudWatch logs shows entries:

11 dispatcher.go:210] Failed calling webhook, failing open mutation.gatekeeper.sh: failed calling webhook "mutation.gatekeeper.sh": failed to call webhook: Post "https://gatekeeper-webhook-service.gatekeeper-system.svc:443/v1/mutate?timeout=1s": no endpoints available for service "gatekeeper-webhook-service"

11 dispatcher.go:214] "Unhandled Error" err="failed calling webhook \"mutation.gatekeeper.sh\": failed to call webhook: Post \"https://gatekeeper-webhook-service.gatekeeper-system.svc:443/v1/mutate?timeout=1s\": no endpoints available for service \"gatekeeper-webhook-service\"" logger="UnhandledError"

Output from the command kubectl get endpoints gatekeeper-webhook-service -n gatekeeper-system:

NAME                         ENDPOINTS   AGE
gatekeeper-webhook-service               2m14s

Any suggestions?

[david-wells-1]

I resolved the issue . The containers were not starting. I pulled the correct image for amd64 using the sha digest and containers starting.