Question 1

What exactly do I get when I create a cluster?

Accepted Answer

A real Kubernetes cluster with its own API server, control plane, and persistent data volume — not a namespace with extra labels. You receive an admin kubeconfig, and normal kubectl, Helm, and CI tools work exactly as they do on any other cluster.

Question 2

Do I need GPUs or accelerators to use KubeCell?

Accepted Answer

No. Accelerators are optional. A host that only offers CPU and memory works fine; you simply publish a quota tier without device requests. The same quota, storage, and isolation model applies either way.

Question 3

Can one developer's workloads starve another's?

Accepted Answer

No. Each cluster has a hard quota for CPU, memory, and accelerators, enforced by Kubernetes on the host. Requests and limits are both capped, so one busy cluster cannot consume another's share.

Question 4

Why does my cluster show only one node?

Accepted Answer

The node is how your cluster sees its quota; the physical machines belong to the host and are managed for you. Need more capacity? Move the cluster to a larger quota tier rather than adding nodes.

Question 5

What happens when I delete a cluster?

Accepted Answer

KubeCell removes the cluster, its credentials, and everything it created on the host. Persistent volumes follow the storage reclaim policy you configured: under Retain they are kept for recovery, so data is never deleted silently.

Question 6

Can two clusters share one GPU?

Accepted Answer

No. Accelerators are allocated as whole cards: a cluster either owns a card or it does not. That keeps performance predictable and makes capacity accounting honest for everyone.

Question 7

Do I need to change my manifests or tooling?

Accepted Answer

No. Workloads inside a cluster are ordinary Pods, Services, Ingresses, and PVCs. There is no sidecar to install and no custom client: your existing kubectl, Helm charts, and CI pipelines work unchanged.

Question 8

How do I expose an app to the internet?

Accepted Answer

Create a normal Ingress in your cluster and choose a name. KubeCell publishes it on the host's shared ingress at a predictable hostname, and TLS is handled at the host level. Ask your platform team for the domain suffix they configured.

Question 9

How long does it take for a cluster to be ready?

Accepted Answer

The first cluster on a host usually takes 10 to 20 minutes because the container images have to be pulled onto the machine. Later clusters start much faster since the layers are already cached.

Question 10

Is KubeCell production ready?

Accepted Answer

Not yet. KubeCell is under active development and the APIs are still v1alpha1. Use it for development, evaluation, and lab environments while the remaining hardening work completes.

Frequently asked questions