Open an issue on GitHub: github.com/boringapps-net/sextant/issues. Include the cluster type (GKE, EKS, AKS, k3s, kind, on-prem etc.), the Kubernetes server version, and a screenshot if the bug is visual.

For anything privacy- or security-sensitive — including suspected vulnerabilities — email hello@boringapps.net directly instead of filing a public issue.

Does Sextant store my credentials? — Bearer tokens, kubeconfig passwords, and client certificates are written to the iOS Keychain (Android Keystore on Android) and never leave your device. See src/lib/storage/clusters.ts in the public source.

Why won't my cluster connect? — Sextant connects directly from your phone to the API server URL you entered, so the server must be reachable from your device's network. Common causes: the API server is behind a VPN, the certificate chain isn't trusted (paste your custom CA into the cluster config), or the bearer token has expired. The error toast usually identifies which.

Does Sextant work with my managed Kubernetes? — Yes — GKE, EKS, AKS, OpenShift, k3s, kind, microk8s, Rancher, and any on-prem distribution that speaks the Kubernetes API. Authenticate with bearer tokens, basic auth, client certificates, or any kubeconfig you can paste in.

Can I try Sextant without exposing my cluster? — Yes. The built-in Demo Cluster is a fully-functional in-memory Kubernetes environment seeded with pods, deployments, services, events, and Helm releases. Tap "Use Demo Cluster" on the onboarding screen.