Documentation
¶
Overview ¶
Command hecate-api serves Hecate's HTTP API.
It exists for the surfaces that cannot hold a kubeconfig — a web UI, a dashboard, a bot — and it is a transport over pkg/ops, so what it answers and what `hecate` prints cannot disagree.
It authenticates nobody itself. A caller presents a Kubernetes bearer token, and Hecate asks the API server who they are and whether they may act. If your cluster authenticates with OIDC then those are OIDC tokens and single sign-on already works; Hecate did not have to know (#73).
Click to show internal directories.
Click to hide internal directories.