Skip to content

FAQ

Open the console, go to Clusters, select Create Cluster, set version/resources, and submit. Use the status column to track progress to Running.

Use GitOps with Argo CD. Keep manifests in Git, sync through Argo, and validate rollout with metrics/logs.

From the cluster view, use the CLI access flow and choose:

  • OIDC kubeconfig for interactive terminal use (requires kubelogin, 24-hour session).
  • Token kubeconfig for automation (expiry selectable up to 365 days).

See CLI Access for full setup details.

Yes. Upgrades are initiated from the console. Follow maintenance windows and validate app compatibility before upgrading.

Yes, but deletion is permanent. Confirm backups/data handling first, then execute delete from the cluster actions dialog.

Billing combines:

  • A monthly plan base fee.
  • Usage-based charges for allocated CPU, memory, and storage.
  • Automatic credit application before payment.

See Billing for details.

Kupe Cloud uses Paddle for payment processing.

Yes. Use HTTPRoute hostnames, automate DNS with ExternalDNS, and manage certificates with cert-manager workflows.

Not yet as a primary workflow. Console-driven management is currently supported. Terraform provider and public API are on the roadmap.

Start with:

  1. Cluster and workload state in console/Headlamp.
  2. Metrics and dashboards.
  3. Logs and events.
  4. Related guide in Operations.