Athena

Using An Existing AthenaClient

Fast path when a platform team has already provisioned the AthenaClient resource for you.

In many teams, a platform or infrastructure engineer creates the AthenaClient resource ahead of time.

If that already exists, you can skip database-URI secret creation and skip defining AthenaClient from scratch.

1) Find The AthenaClient

List them:

kubectl get athenaclient -A

Inspect one in detail:

kubectl get athenaclient <name> -n <namespace> -o yaml

Key fields to check:

  • spec.clientName
  • spec.gatewayRef
  • spec.pgUriSecretRef

2) Make Sure The Referenced Secret Exists

The pgUriSecretRef secret normally needs to exist in the same namespace as the AthenaClient.

kubectl get secret <secret-name> -n <namespace>

3) Verify The AthenaClient Is Ready

kubectl describe athenaclient <name> -n <namespace>

If it is not ready, inspect operator logs:

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

If you are running the operator locally, check the terminal running go run ./cmd/athena-operator.

4) Common Next Step

Once AthenaGateway and AthenaClient are healthy, the next step is usually API keys.

Deploy Gateway

Deploy Athena Gateway with the AthenaGateway custom resource and the required admin-key secret.

Create An AthenaClient

Create a database-backed AthenaClient resource and the secret it depends on.

On this page

1) Find The AthenaClient2) Make Sure The Referenced Secret Exists3) Verify The AthenaClient Is Ready4) Common Next Step