You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cluster-autoscaler/cloudprovider/hetzner/README.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ The cluster autoscaler for Hetzner Cloud scales worker nodes.
22
22
"arm64": "",
23
23
"amd64": ""
24
24
},
25
+
"ipRange": "10.0.0.0/16", // Optional, make sure to match your private network configuration and to use the cidr notation - if not set the hetzner cloud default will be used
25
26
"nodeConfigs": {
26
27
"pool1": { // This equals the pool name. Required for each pool that you have
27
28
"cloudInit": "", // HCLOUD_CLOUD_INIT make sure it isn't base64 encoded twice ;]
@@ -47,7 +48,11 @@ Can be useful when you have many different node pools and run into issues of the
47
48
48
49
**NOTE**: In contrast to `HCLOUD_CLUSTER_CONFIG`, this file is not base64 encoded.
49
50
50
-
The global `imagesForArch` configuration can be overridden on a per-nodepool basis by adding an `imagesForArch` field to individual nodepool configurations.
51
+
The `ipRange` configuration can be used to place nodes within a specific IP range. This only applies to private networks. Make sure that the IP range is within the configured private network IP Range. If you do not set this value, the default setting from Hetzner Cloud will be used.
52
+
53
+
Following global configuration options can be overriden on a per-nodepool basis by adding them to the individual nodepool configurations:
0 commit comments