What you decide at each step.
The stepper contains eleven fixed stages. HAProxy / Load Balancer appears after Cluster when the profile requires it. Each stage prepares information used later, leading to review of the complete plan.
The desktop workflow uses Windows and a local Docker runtime. You supply compatible hosts, connectivity and credentials with the required permissions. Sizing and operating systems must match the chosen scenario.
Server, connectivity, license and provider service costs remain your responsibility.
An environment profile is a technical decision. Free, Pro and Team are proposed commercial plans; choosing a plan does not change topology requirements.
Cluster
What you configure or inspect
- Cluster name
- Environment
- Internal cluster domain
Identify the environment and establish the profile that determines minimum host counts and the need for API load balancing.
HAProxy / Load Balancer
Shown when required by the profile; mandatory for Prod.
What you configure or inspect
- HAProxy host IPs
- VIP / load balancer IP
- Kubernetes API domain
Define the stable API endpoint. The Prod profile requires two HAProxy hosts and a VIP in addition to Kubernetes nodes.
Control plane
What you configure or inspect
- Control plane IPs
- Host count required by the profile
Choose the hosts that run the cluster control plane. Prod requires at least three; distribution should match your availability requirements.
Worker nodes
What you configure or inspect
- Worker IPs
- Adding and removing hosts in the plan
Allocate the infrastructure that will run workloads and components. Prod requires at least three workers; storage and capacity can require additional resources.
Network
What you configure or inspect
- Pod CIDR
- Service CIDR
- Cilium LoadBalancer pool name and CIDR
Separate network ranges and choose the address pool used for exposure. These values must be compatible with host networking and the environment.
Access & Readiness
What you configure or inspect
- Connection parameters and local credential
- Per-host checks
- Discovered capacity and disks
Confirm access and prerequisites before execution. Results also inform the following storage and capacity decisions.
Storage
What you configure or inspect
- Enabling Rook-Ceph
- Eligible device per worker
- Confirmations for disks containing data
Choose where data will persist and review device suitability. The current workflow requires eligible disks on at least three workers for Rook-Ceph.
Ingress / Gateway
What you configure or inspect
- Cilium Gateway or Istio for the scenario
- Application domain or hostname
- TLS certificate and coverage
Connect traffic, names and certificates. Preserve the distinction between infrastructure and application access and check how clients will reach the Gateway.
Platform Engineering
What you configure or inspect
- Platform components
- Component-specific configuration
- Applicable persistence and dependencies
Assemble the delivery, data and operational tools appropriate for the team. Review supported profiles before assuming redundancy or capacity.
Observability
What you configure or inspect
- Metrics, logs, traces and profiles
- Available volume and retention settings
- Collectors and stack dependencies
Decide which signals to collect and for how long. The selection must fit storage and have a compatible collection path.
Security, Identity & Policy
What you configure or inspect
- Identity, policy and security tools
- Replicas and persistence for each component
- Dependencies and controls offered by the profile
Configure each tool’s responsibilities. Keycloak distinguishes local and external databases; its local database remains a single replica. HA Vault requires suitable persistence and replicas, plus operational initialization and unseal preparation.
Review
What you configure or inspect
- Consolidated topology
- Selections and planned resources
- Validation and execution action
Review the complete plan before Apply. Correct decisions while they are still configuration; the console follows execution started in the application.
Installation is the start of operations.
Review the plan, start installation and follow commands and results in the console. The workflow validates Kubernetes readiness after installation and organizes application access.
Duration depends on infrastructure, network speed and selected components. There is no guaranteed completion time for every environment.
Use Navigator to explore resources, events, YAML, logs and available operational access. Access Center collects endpoints and access information to reduce searching across scattered details.
Planning, updates, policies, backups and recovery remain operational responsibilities. Use vendor documentation and validate changes in your environment.
Explore NavigatorReferences for planning your environment
Consult official documentation and confirm requirements for your chosen versions before operating in production.
