If the cluster control plane is hosted on a virtual machines or bare-metal servers, the cloud provider uses the settings from the
cloud-provider-zvirt
module in the Deckhouse configuration. Otherwise, if the cluster control plane is hosted in a cloud, the cloud provider uses the ZvirtClusterConfiguration structure for configuration.
ZvirtClusterConfiguration
Version: deckhouse.io/v1
Describes the configuration of a cloud cluster in zVirt.
Used by the cloud provider if a cluster’s control plane is hosted in the cloud.
Run the following command to change the configuration in a running cluster:
kubectl -n d8-system exec -ti svc/deckhouse-leader -c deckhouse -- deckhouse-controller edit provider-cluster-configuration
After updating the node parameters, you need to run the dhctl converge command to apply the changes.
Example:
apiVersion: deckhouse.io/v1
kind: ZvirtClusterConfiguration
layout: Standard
clusterID: b46372e7-0d52-40c7-9bbf-fda31e187088
masterNodeGroup:
replicas: 1
instanceClass:
numCPUs: 4
memory: 8192
template: debian-bookworm
vnicProfileID: 49bb4594-0cd4-4eb7-8288-8594eafd5a86
storageDomainID: c4bf82a5-b803-40c3-9f6c-b9398378f424
nodeGroups:
- name: worker
replicas: 1
instanceClass:
numCPUs: 4
memory: 8192
template: debian-bookworm
vnicProfileID: 49bb4594-0cd4-4eb7-8288-8594eafd5a86
provider:
server: "<SERVER>"
username: "<USERNAME>"
password: "<PASSWORD>"
insecure: true
- string
Required value
The way resources are located in the cloud.
Read more about possible provider layouts.
- object
Required value
The definition of the master’s NodeGroup.
For the changes to take effect, run
dhctl converge
after modifying the parameters of themasterNodeGroup
section.- string
Required value
Storage domain id which contains the shared resources that must be available to all datacenter hosts.
Pattern:
^[\da-fA-F]{8}\-[\da-fA-F]{4}\-4[\da-fA-F]{3}\-[\da-fA-F]{4}\-[\da-fA-F]{12}$
Example:
storageDomainID: 49bb4594-0cd4-4eb7-8288-8594eafd5a86
- array of objects
An array of additional NodeGroups for creating static nodes (e.g., for dedicated front nodes or gateways).
- object
The same as the
metadata.annotations
standard field.Example:
annotations: ai.fleet.com/discombobulate: 'true'
- object
A list of labels to attach to cluster resources.
The same as the
metadata.labels
standard field.Example:
labels: environment: production app: warp-drive-ai
- array of objects
The same as the
.spec.taints
field of the Node object.Available fields:
effect
,key
, andvalues
.Example:
taints: - effect: NoExecute key: ship-class value: frigate