Kubernetes & KubeUI

Kubernetes isn't an add-on you bolt on later — it's built into SkyVirtHCI. From the same console that runs your virtual machines, you provision complete Kubernetes clusters, manage them through a visual dashboard, and give their stateful workloads the same resilient storage your VMs use. There's no second platform to license, stand up or learn.

Provision a cluster

Creating a cluster is a form, not a project. Choose how many control-plane and worker nodes you want and how big each should be; the platform builds the cluster — control plane, workers, in-cluster networking and storage integration wired up — and hands you a working kubeconfig a few minutes later.

• Isolated per tenant. A cluster belongs to a tenant like any other resource, on that tenant's networks and against its quotas — teams, classes or customers each get their own, cleanly separated on shared hardware.
• Grow and shrink. Add or remove worker nodes as demand changes; the cluster absorbs them without disruption.
• Standards-compliant. It's ordinary, conformant Kubernetes — your existing manifests, Helm charts and kubectl workflows work unchanged.

SkyVirt KubeUI — see and drive every cluster

Every cluster comes with SkyVirt KubeUI, a clean visual dashboard so you don't have to live in a terminal to understand what's running:

• At a glance: workloads, nodes, namespaces and events across the cluster, with live status and resource use.
• Drill in: inspect pods, deployments and services, read logs, and follow what a workload is actually doing.
• Day-to-day operations — scale, restart, inspect and troubleshoot — from the browser, alongside the rest of your infrastructure.

SkyVirt KubeUI is published and open at github.com/straightarctech/skyvirt-kubeui. It reaches each cluster on its published address, so it works the same whether you're online or fully air-gapped.

Persistent storage, from SkyVirtStore

Stateful workloads — databases, queues, object stores — need durable disks. In SkyVirtHCI those come straight from SkyVirtStore, the platform's own storage engine: request a persistent volume in Kubernetes and it's carved from the same replicated, self-healing pool your VMs use, with the same mirroring, deduplication and online growth. Containers and VMs share one storage fabric — there's no separate storage system to run for either.

Protecting Kubernetes applications

Kubernetes workloads are protected the same way everything else is: scheduled, application backups capture a cluster's resources and the data on their persistent volumes, and restore brings an application back — to the same cluster or a different one. That folds Kubernetes into the same backup and disaster-recovery story as your virtual machines, rather than leaving it as a gap you cover with yet another tool.