ankra-cli

Provision and manage Ankra-managed Kubernetes clusters (K3s or kubeadm) on Hetzner Cloud, OVHcloud, UpCloud, and DigitalOcean - creating clusters, storing provider credentials, and managing node groups, scaling, Kubernetes versions, and upgrades. Use when the user wants to create or provision a new Kubernetes cluster (rather than import an existing one), or mentions Hetzner, OVH, UpCloud, or DigitalOcean clusters.

Configure alerting and notifications for Kubernetes clusters through Ankra - alert rules and outbound webhooks that notify Slack, Microsoft Teams, Discord, PagerDuty, Opsgenie, Datadog, or custom endpoints, with automatic AI incident analysis attached to alerts. Use when the user wants alerting, notifications, incident routing, or on-call integration for a Kubernetes cluster in an Ankra environment.

Build CI/CD pipelines (GitHub Actions or GitLab CI) that deploy to Kubernetes the GitOps way - build a container image, push it with an immutable tag, and bump that tag in the Ankra GitOps repository so Ankra/ArgoCD syncs the change, rather than running kubectl/helm against the cluster from CI. Use when the user sets up CI/CD or automated deployment to a Kubernetes cluster in an Ankra environment, or asks how to deploy on push.

Drive the Ankra CLI to log in, select an organisation and cluster, apply cluster/stack YAML, inspect pods, logs, events, and metrics, triage operations, and chat with Ankra AI. Use for day-to-day Kubernetes work whenever the `ankra` CLI is installed - checking what runs on a cluster, applying changes, debugging workloads, connecting kubectl - not only when the user names Ankra explicitly.

Structure a GitOps repository for Kubernetes with Ankra - modular include paths so cluster and stack definitions are stored in Git and synced by Ankra/ArgoCD. Use when the user sets up GitOps, connects a Git repository to a cluster, organizes cluster/stack YAML in a repo, or wants Git to be the source of truth for their Kubernetes configuration.

Connect HTTP and OCI Helm chart registries to Ankra and store least-privilege registry credentials (Harbor, Nexus, JFrog Artifactory, ChartMuseum, GHCR, Amazon ECR, Google Artifact Registry, Azure Container Registry, Docker Hub). Use when the user needs charts from a private registry on a Kubernetes cluster, or mentions Helm registries, OCI registries, or registry credentials.

Author and apply an Ankra ImportCluster YAML manifest that connects an existing Kubernetes cluster (EKS, GKE, AKS, k3s, on-prem, ...) to the Ankra platform, wires a GitOps repository, and declares stacks of manifests and Helm addons with dependency ordering. Use when the user wants to import, onboard, or connect an existing Kubernetes cluster to a management platform, write a cluster.yaml / ImportCluster file, or apply one with `ankra cluster apply`.

Deploy monitoring and logging on a Kubernetes cluster through Ankra (Prometheus, Grafana, Loki, Promtail) and wire external Prometheus-compatible metrics sources (Grafana Cloud, Amazon Managed Prometheus, Google Cloud Managed Prometheus, Thanos, VictoriaMetrics). Use when the user wants monitoring, metrics, dashboards, or logging on a Kubernetes cluster in an Ankra environment, or to connect a metrics source to Ankra.

Cross-cutting best practices for building and operating Kubernetes with Ankra - Git as source of truth, pinned versions, variables over hardcoding, least-privilege credentials, promotion through environments, idempotent operations, and explicit confirmation for destructive actions. Use for ANY Kubernetes task in an environment with the `ankra` CLI or an Ankra GitOps repo - deploying, upgrading, debugging, or reviewing clusters, stacks, or CI/CD - and read it before reaching for kubectl or helm directly.

Encrypt Kubernetes Secrets and sensitive values stored in Git using SOPS with AGE, tracked with encrypted_paths so Ankra decrypts at deploy time. Use when the user needs to put secrets, credentials, or API keys into Kubernetes configuration stored in a repo, or mentions SOPS, AGE, encrypted_paths, or `ankra cluster encrypt`/`decrypt`/`sops-config`.

Compose Ankra Stacks from Helm addons, raw Kubernetes manifests, variables, and dependency edges that control deployment order. Use when deploying anything onto an Ankra-managed Kubernetes cluster - installing a Helm chart or addon (ingress-nginx, cert-manager, Prometheus, databases, ...), applying manifests, ordering resources with parents or deploy waves - instead of running helm install or kubectl apply directly.

Manage Ankra resources as infrastructure-as-code with the Ankra Terraform provider - clusters, stacks, addons, credentials, and tokens declared in HCL and reconciled by `terraform apply`. Use when the user manages their Kubernetes platform with Terraform or IaC, mentions the Ankra provider, or wants clusters and stacks declared in HCL.