Hecate

Settings

What this installation is connected to, and who may use it.

This installation

Version…
Signed in as…

Logs and traces

Hecate stores neither. Logs are written to stdout and collected by your cluster; traces go to the collector below.

kubectl -n hecate-system logs -l app.kubernetes.io/name=hecate -f
kubectl -n hecate-system logs -l app.kubernetes.io/component=api -f
Trace endpointnot configuredSet otel.endpoint in the chart to export spans.

Evidence servers

No Gate names an evidence server.

This edits the Gate in the cluster. If it is reconciled from git, Flux restores the committed value on the next sync — change it there to make it stick.

Connected clusters

Other clusters this installation can promote into. The cluster Hecate runs in is not one of these — it needs no credentials and is always available.

Nothing connected, and Hecate is not running inside a cluster either — so it is reaching Kubernetes with whatever kubeconfig it was started with.

Stored under the key value, the same convention Flux uses. A Gate still only sees its own namespace on the remote cluster — a cluster reference is not a way around the tenant rule.

Use a credential that does not expire. A bound service-account token — what kubectl create token gives you by default — lasts an hour or a day, and the connection stops working when it runs out.