Troubleshooting

Check The Basics

kubectl config current-context
kubectl get nodes

Operator Logs

If the operator runs in-cluster:

kubectl logs -n athena-operator-system deploy/athena-operator -f

If it runs locally, inspect the terminal running:

go run ./cmd/athena-operator

"expected exactly 1 AthenaGateway"

If more than one AthenaGateway exists, related resources such as AthenaClient and AthenaApiKey should set spec.gatewayRef.

Secret Namespace Gotchas

Secrets are namespaced, so the referenced resource and the secret have to line up correctly:

• AthenaGateway.spec.adminKeySecretRef must be in the gateway target namespace
• AthenaClient.spec.pgUriSecretRef must be in the AthenaClient namespace
• AthenaApiKey.spec.writeSecretRef must be in the AthenaApiKey namespace

Kubernetes Events

kubectl get events -A --sort-by=.lastTimestamp

See What Kubernetes Actually Created

Gateway workload:

kubectl get deploy,svc -n athena-system
kubectl get pods -n athena-system -l app.kubernetes.io/name=athena-gateway

Operator workload:

kubectl get deploy,pods -n athena-operator-system