Skip to content

FAQ

Open the console, go to Clusters, select Create Cluster, choose the Kubernetes version and resource limits, and submit. Use the cluster status to track progress until it reaches Running.

Use GitOps with Argo CD. Keep your manifests in Git, create an Argo CD Application, and validate rollout with logs, metrics, and dashboards.

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

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

See CLI Access for full setup details.

Yes. Upgrades are initiated from the console. Plan for a maintenance window and validate workload compatibility before rolling the version forward.

Yes, but deletion is permanent. Confirm backups, data handling, and workload migration first, then delete the cluster from the console.

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 for routing, and use the custom-domain flow when you want to serve traffic on your own domain. Kupe handles certificate issuance and HTTPS for the supported routing paths.

Yes. Kupe Cloud supports both a Terraform provider and a public API, alongside the console. Use the console for interactive workflows, Terraform for infrastructure as code, and the API for direct automation and custom integrations.

See Terraform and API.

Secrets are stored in a dedicated vault that Kupe manages for you. You define the secret once, then sync it to one or more cluster and namespace targets.

Deleting a secret removes it from the vault, but already-synced Kubernetes Secret objects are not removed automatically. See Secrets.

Use Grafana for both. Logs are available in Grafana Explore through Loki, and metrics are available through dashboards and PromQL queries.

See Observability.

Start with:

  1. Cluster and workload state in console/Headlamp.
  2. Logs, metrics, and dashboards in Grafana.
  3. Routing and domain configuration if the issue is traffic-related.
  4. The most relevant guide for the workflow you are working on.