Experimental version. The functionality may undergo significant changes. Compatibility with future versions is not guaranteed.
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-dynamix
module in the Deckhouse configuration. If the cluster control plane is hosted in a cloud, the cloud provider uses the DynamixClusterConfiguration structure for configuration.
DynamixClusterConfiguration
Version: deckhouse.io/v1
Describes the configuration of a cloud cluster in Dynamix.
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 deploy/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: DynamixClusterConfiguration
layout: StandardWithInternalNetwork
sshPublicKey: ssh-rsa AAAA
location: dynamix
account: acc_user
nodeNetworkCIDR: 10.241.32.0/24
nameservers:
- 10.0.0.10
provider:
controllerUrl: "<controller url>"
oAuth2Url: "<oAuth2 url>"
appId: "<app id>"
appSecret: "<app secret>"
insecure: true
masterNodeGroup:
replicas: 1
instanceClass:
numCPUs: 6
memory: 16384
rootDiskSizeGb: 50
imageName: "<image name>"
storageEndpoint: "<storage endpoint>"
pool: "<pool>"
externalNetwork: "<external network>"
nodeGroups:
- name: worker
replicas: 1
instanceClass:
numCPUs: 6
memory: 16384
rootDiskSizeGb: 50
imageName: "<image name>"
externalNetwork: "<external network>"
- 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. - 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