Starting installation
Have you chosen a license? Then proceed to installation. If not, request a CE license (via the website form or Telegram bot) or contact a Shturval product representative for an enterprise license.
- Determine the installation environment:
- Open (all cluster hosts require access to r.shturval.tech on port 443)
- Closed (enterprise only! Before installation, prepare the mirror using the bundle provided by your manager.)
- Choose an infrastructure provider:
2.1. With the Shturval v2 provider, prepare hosts with one of the OS versions listed in the cluster node OS table:
- 1 Control Plane (6/8/80) for minimum configuration;
- 3 Control Plane (4/16/100) and 3 Worker (8/32/300) for high availability;
- for closed-environment installation, add 1 host (2/4/150) for the mirror;
- with network segmentation, allocate a separate host (bastion/jumphost) to run shtil with one of the supported OS versions (do not plan to add this host as a cluster node).
2.2. For installation with one of these providers: oVirt (zVirt, oVirt, HostVM, RED Virtualization, ROSA Virtualization), vSphere, OpenStack (VK Cloud, Selectel), prepare a virtual machine template.
If needed after installation, you can add hosts to the Shturval v2 provider when the cluster was created with Shturval v2, or scale nodes for clusters with oVirt, vSphere, or OpenStack providers.
Verify:
- SELinux is disabled or permissive on hosts;
- cgroup v2 is enabled on cluster nodes;
- time is synchronized between hosts and your workstation;
- unavailable repositories (for example, distribution defaults) are removed from hosts (only iptables and gnupg are required).
- Create a user on each host (for example, shturval). This user must be able to run sudo without a password.
- You can use an external or internal load balancer for KubeAPI and/or Ingress:
- With an external load balancer, each component needs an FQDN (network interaction examples)
- Without an external load balancer, prepare 2 non-pingable (free) IP addresses. They must not be configured on any cluster host, but must be in the same subnet as Control Plane hosts.
- Prepare certificates for installation, or proceed without them to install self-signed certificates.
- Start installation with the shtil utility. You can install using either:
Note
- Use a machine that is not planned as a cluster node to run shtil.
- When running shtil on a VM or bastion/jumphost, the user must be able to perform port forwarding.
NTP configuration on cluster nodes is not available during installation. The default timezone is Europe/Moscow. After installation, you can configure NTP on cluster nodes using the NCI resource.