This demo walks through the full first-cluster flow in Safespring Kubernetes Engine: from signing in to the portal and creating a cluster to connecting with kubectl and removing the demo cluster when it is no longer needed.
The walkthrough starts in the Safespring self-service portal, where environments are used to group resources. From an empty environment, the demo creates a new Kubernetes cluster and shows the choices made during provisioning, including data center, control plane sizing and worker node sizing.
The cluster is created in Stockholm 2 as an example. The configuration review shows the selected data center, cluster name, control plane nodes, worker nodes and the downloadable configuration before the request is submitted.
During provisioning, the demo explains what Safespring sets up around the cluster: the managed control plane, worker nodes, API endpoint, automatically provisioned DNS for ingress and the Talos Linux base used for the nodes. It also covers how Kubernetes upgrades are handled, including when changes need coordination with the application team.
After the cluster becomes active, the overview page shows region, Kubernetes version, Talos version, network details, API endpoint, ingress CNAME target and worker node count. The demo then scales the worker pool from three to four nodes directly from the portal.
The second half focuses on access. The kubeconfig contains the cluster certificate authority data, API server endpoint and login configuration for the data center identity provider. Portal access and cluster access are intentionally separated, so administrators can create or remove clusters while cluster users authenticate to the data center without needing permission to delete infrastructure.
Finally, the demo logs in with kubectl, lists nodes and checks pods in the kube-system namespace. The walkthrough points out components such as Cilium, CoreDNS and CSI Cinder before deleting the demo cluster.
Demo 1
