Skip to content

FAQ

The questions that come up most once you’re actually running clusters: creating and upgrading them, deploying to them, and understanding backups and supported features.

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 Cluster 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.

Can I delete my tenant or my user account?

Section titled “Can I delete my tenant or my user account?”

Yes, both, without asking us. Only the tenant owner can delete a tenant, and a user account can only be deleted once it belongs to no tenant. Both are permanent. See Deletion for what each one destroys, what is kept, and the console, CLI, and API steps.

Email support@kupe.cloud, and check status.kupe.cloud first if the platform looks broken. Support lists the other routes and what to include in a bug report.

Kupe does not back up your workloads, persistent volumes, or in-cluster Kubernetes state. Keep manifests in Git and make independent backups of application data.

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.

Create secrets in the console. You define the secret once, then sync it to one or more cluster and namespace targets.

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

Yes, PostgreSQL. A database belongs to your tenant and is bound into the cluster namespaces that use it. Start with Add a database to your application, and see the Databases FAQ for what databases do not do, including backups.

Yes. Each tenant can turn on one private registry at registry.kupe.cloud/<tenant>. Connect a cluster and every pod in it pulls your images without imagePullSecrets; CI pushes with an access token. See Registry.

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

See Observability.

Start with:

  1. Cluster and workload state in the console.
  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.