YAML constructor (Shturval v2)

Step-by-step Shturval v2 provider parameters and download of two YAML files.

This constructor helps you prepare YAML manifests to install a management cluster with the Shturval v2 provider via ./shtil install-cli shturvalv2 --yaml-path=….

The result is two files: CapsmProviderConfig (provider) and CapsmClusterConfig (cluster). For the full installation process and field reference, see the Open loop installation process or Closed loop installation process page (Installation with YAML tab).

Important: Values you enter (including passwords and key paths) are stored only in browser memory while you use this page. Data is not sent to the server and not saved—when you leave the page, the form resets.

On the Provider step, specify SSH credentials and the host list. The first host uses the controlplane role; every other host uses a label that matches a node group’s Host role (by default workers). If sudo asks for a password, fill in SSH user password: the shared value is written to credentials.SSH.sshUserPassword, and a host value is written to hosts[].credentials.SSH. You can override the host user name and key; if the host-specific fields are empty, the host uses the shared credentials. On the Cluster step, configure Ingress, load balancers, services, provider overwrite, and the installation log file. The Ingress certificate, including Vault, is written to ingressCerts in the provider file. On the Nodes step, set groups: name, Kubernetes role (workers or infra), host role, and count. These values are written to workerNodeConfigs as groupName, roles, workersCount, and workerSelector.matchLabels.role. provider.name in the cluster document is the provider instance name. The console flag --ssh-user-password is described in SSH user password for sudo.

Reference: service groups

Below are the quick-install groups from Shturval repository services.

Enabled services lists only extra services on top of the default set: critical platform services and the Monitoring and Logging groups are enabled by default. An unknown service name is ignored. The minimal service set installs only critical platform services. When you select a service, the constructor adds its dependent CRDs if those CRDs are also disabled by default. CSI, NFS, Ceph, Multus, SR-IOV, and provider charts are not in this list: they cannot be added as extra services.

The management cluster receives incoming HTTP traffic through Gateway API by default. shturval-gateway-api-crds is a critical service. The external connections module (shturval-ingress-controller) is installed in absent mode.

Group nameService nameSystem name
Critical ServicesCluster network managementshturval-networking
Local storageshturval-local-csi
snapshotter operatorshturval-snapshotter
Host Configuration Managementshturval-node-config
Service Installation Managementshturval-services
Cluster updateshturval-update
Virtual IP (node configuration)shturval-vip
Virtual IP (service configuration)shturval-vip-provider
Local DNSshturval-caching-dns
TLS Certificate Managementshturval-cert-manager
Delivery of root certificatesshturval-trust-manager
External connections (Ingress)shturval-ingress-controller
CRD Gateway APIshturval-gateway-api-crds
Critical management cluster servicesSoftware Control Chartshturval-backend
Graphical platform control moduleshturval-frontend
Authenticationshturval-auth
Cluster API Providershturval-capi
Client Cluster Managershturval-cluster-manager
Management Cluster ServicesCentralized storage of metricsshturval-monitoring
Provider Basis Dynamixshturval-capbd
OpenStack Providershturval-capos
Provider Shturval v2shturval-capsm
vSphere Providershturval-capvs
Provider oVirtshturval-capov
Yandex Cloud Providershturval-capy
vCloud Director Providershturval-capvcd
MonitoringMetrics collection and monitoring managementshturval-metrics-collector
Visualization of metricsshturval-dashboards
Verifying Kubernetes API Certificatesshturval-cert-expiration
LoggingLocal log collectionshturval-log-collector
Backup and RestoreBackup and Restoreshturval-backup
Application DeliveryApplication Service Deployment Managementshturval-rollouts
Continuous Application Deliveryshturval-cd
Load BalancerNode Load Distributionshturval-descheduler
Information Security ToolsApplication Configuration Analysisshturval-policy-manager
Scanning container imagesshturval-scanner
Optional services not in groupsNFS operatorshturval-nfs-csi
Ceph CSI - Ceph File Systemshturval-ceph-cephfs
Ceph CSI - Ceph Block Deviceshturval-ceph-rbd
oVirt CSIshturval-capov-csi
CSI vSphereshturval-capvs-csi
vCloud Director CSIshturval-capvcd-csi
CSI OpenStackshturval-capos-csi
Search for nodes with hostport servicesshturval-coreha
Multiple network interfaces (Multus)shturval-metacni
IP assignment on Multus interfacesshturval-metacni-ipam
SR-IOV Operatorshturval-sriov
Node problem detectionshturval-npd

No services for the selected group

For the full chart list with versions and descriptions, see Shturval repository services.

YAML constructor (Shturval v2)

Walk through the steps to generate two YAML manifests: provider and cluster. Download the files and pass the combined manifest path to install-cli. Values stay in the browser only and are cleared when you leave the page.

Review the YAML and download the files. Data is not saved after you leave the page.

After downloading, merge both documents into one file with a --- separator, or pass the path to the combined manifest to install-cli:

./shtil install-cli shturvalv2 \
  --yaml-path="/home/admin/install.yaml" \
  --bootstrap-license="YOUR-LICENSE"

You can also get the current field structure and comments with ./shtil install-cli shturvalv2 example.