kcli-cluster-deployment

To deploy a Kubernetes cluster with kcli, you create a new cluster by specifying a cluster type and name. This automates parameter-driven cluster provisioning across multiple providers using local kcli installations.

Yes, kcli supports deploying OpenShift, k3s, kubeadm, hypershift, microshift, and generic Kubernetes clusters. It automates deployment and lifecycle management across these distributions.

You need a local kcli installation and access to cluster state stored under ~/.kcli/clusters. Parameter-driven configuration is also required to automate deployments across providers.

You can scale existing Kubernetes clusters using kcli's lifecycle management operations. The tool supports create, scale, and get kubeconfig operations, alongside context-aware diagnostics and state persistence.

Using kcli enables automated, parameter-driven cluster deployments across multiple providers. It handles OpenShift, k3s, kubeadm, and generic Kubernetes distributions while persisting cluster state locally.

Kcli cluster deployment requires access to ~/.kcli/clusters to maintain context-aware diagnostics and state persistence. This directory stores the local cluster state needed for lifecycle management operations.