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: docs/configuration/environment.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,7 @@ The CCM supports the following flags:
53
53
|`--enable-ipv6-for-loadbalancers`|`false`| Set both IPv4 and IPv6 addresses for all LoadBalancer services (when disabled, only IPv4 is used). This can also be configured per-service using the `service.beta.kubernetes.io/linode-loadbalancer-enable-ipv6-ingress` annotation. |
54
54
|`--node-cidr-mask-size-ipv4`|`24`| ipv4 cidr mask size for pod cidrs allocated to nodes |
55
55
|`--node-cidr-mask-size-ipv6`|`64`| ipv6 cidr mask size for pod cidrs allocated to nodes |
56
+
|`--disable-ipv6-node-cidr-allocation`|`false`| disables allocating ipv6 CIDR ranges to nodes when using CCM for node IPAM (set to `true` if ipv6 ranges are not configured on linode interfaces) |
Copy file name to clipboardExpand all lines: docs/configuration/nodeipam.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Note:
21
21
Make sure node IPAM allocation is disabled in kube-controller-manager to avoid both controllers competing to assign CIDRs to nodes. To make sure its disabled, check and make sure kube-controller-manager is not started with `--allocate-node-cidrs` flag.
22
22
23
23
## Allocated subnet size
24
-
By default, CCM allocates /24 subnet for ipv4 addresses and /64 for ipv6 addresses to nodes. If one wants different subnet range, it can be configured by using `--node-cidr-mask-size-ipv4` and `--node-cidr-mask-size-ipv6` flags.
24
+
By default, CCM allocates /24 subnet for ipv4 addresses and /112 for ipv6 addresses to nodes. For ipv6 cidr allocation using CCM, linodes should have ipv6 ranges configured on their interfaces. If one wants different subnet range, it can be configured by using `--node-cidr-mask-size-ipv4` and `--node-cidr-mask-size-ipv6` flags.
25
25
26
26
```yaml
27
27
spec:
@@ -31,7 +31,10 @@ spec:
31
31
- name: ccm-linode
32
32
args:
33
33
- --allocate-node-cidrs=true
34
-
- --cluster-cidr=10.192.0.0/10,fd00::/56
34
+
- --cluster-cidr=10.192.0.0/10
35
35
- --node-cidr-mask-size-ipv4=25
36
36
- --node-cidr-mask-size-ipv6=64
37
37
```
38
+
39
+
## Disabling ipv6 ipam allocation
40
+
If one wants to just use ipv4 node ipam allocation for their nodes, they can start CCM with `--disable-ipv6-node-cidr-allocation=true` which disables ipv6 range allocation to nodes.
Copy file name to clipboardExpand all lines: main.go
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -98,6 +98,7 @@ func main() {
98
98
command.Flags().IntVar(&linode.Options.NodeBalancerBackendIPv4SubnetID, "nodebalancer-backend-ipv4-subnet-id", 0, "ipv4 subnet id to use for NodeBalancer backends")
99
99
command.Flags().StringVar(&linode.Options.NodeBalancerBackendIPv4SubnetName, "nodebalancer-backend-ipv4-subnet-name", "", "ipv4 subnet name to use for NodeBalancer backends")
100
100
command.Flags().BoolVar(&linode.Options.DisableNodeBalancerVPCBackends, "disable-nodebalancer-vpc-backends", false, "disables nodebalancer backends in VPCs (when enabled, nodebalancers will only have private IPs as backends for backward compatibility)")
101
+
command.Flags().BoolVar(&linode.Options.DisableIPv6NodeCIDRAllocation, "disable-ipv6-node-cidr-allocation", false, "disables IPv6 node cidr allocation by ipam controller (when enabled, IPv6 cidr ranges will be allocated to nodes)")
0 commit comments