https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/Recent content in Workers onHugo -- gohugo.ioTue, 06 Oct 2020 08:48:23 +0000https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/worker-group/Tue, 06 Oct 2020 08:49:31 +0000https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/worker-group/Worker node groups are groups of nodes that run the cluster workload. By default, 2 groups of Worker nodes are created in the Shturval platform: Infra and Default, and it is also possible to create additional groups. A group of infrastructure nodes will preferably be used to deploy the cluster’s infrastructure services. If there are no free nodes in the group, services will be deployed on Worker nodes of other groups.https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/capi/Tue, 06 Oct 2020 08:49:31 +0000https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/capi/When creating a new group in the ClusterAPI Configuration block, it is possible to specify the ClusterAPI, MachineDeployment parameters. The group name is formed according to the rule: the name of the cluster with a postfix in the form of the requested group name. Screenshot of group creation When viewing the group configuration on the ClusterAPI Configuration tab, you can change the ClusterAPI, MachineDeployment parameters. Screenshot of node group configuration Selecting a method for scaling nodes in a group: Manual.https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/inframachinetemplate/Tue, 06 Oct 2020 08:49:31 +0000https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/inframachinetemplate/When creating a new group of Worker nodes in the InfraMachineTemplate block, it is possible to configure the parameters of the infrastructure template. When viewing the group configuration on the InfraMachineTemplate tab, you can change the settings by manually applying new values ​​or copying values ​​from another existing template. Depending on the type of provider, the resource is edited/created: -OVirtMachineTemplate; VSphereMachineTemplate; OpenStackMachineTemplate; BasisMachineTemplate; ShturvalMachineTemplate; YandexMachineTemplate; VCDMachineTemplate. More detailed settings for infrastructure templates can be configured in the management cluster in the Administration/Custom Resources section using a custom resource of the corresponding provider in the infrastructure.https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/machinehealthcheck/Tue, 06 Oct 2020 08:49:31 +0000https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/machinehealthcheck/For the Worker group of nodes on the MachineHealthCheck tab you can: Screenshot configure different MachineHealthCheck configurations to check the health of machines. When installing a client cluster, the default MachineHealthCheck is mounted for each group of Worker nodes. To configure additional MachineHealthChecks, click +Add. When multiple configurations have been created, the tab displays a list of MachineHealthChecks. go to viewing and editing the MachineHealthCheck configuration. To configure MachineHealthCheck: set the name MachineHealthCheck.https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/autoscaler/Tue, 06 Oct 2020 08:49:31 +0000https://docs.shturval.tech/2.13/en/cluster-admin/c-administration/nodes/workers/autoscaler/Cluster Autoscaler in ClusterAPI provides a mechanism for changing the number of nodes in a cluster depending on the load on the nodes. Autoscaling allows you to optimize resources under variable load in Kubernetes clusters. The main purpose of Cluster Autoscaler is to provide nodes to Pods waiting to be launched. Cluster Autoscaler can only manage autoscaling on groups of Worker nodes. It monitors the state of pods, nodes in the cluster and: