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/annotations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ The keys and the values in [annotations must be strings](https://kubernetes.io/d
40
40
|`firewall-acl`| string || The Firewall rules to be applied to the NodeBalancer. See [Firewall Configuration](#firewall-configuration)|
41
41
|`nodebalancer-type`| string || The type of NodeBalancer to create (options: common, premium, premium_40gb). See [NodeBalancer Types](#nodebalancer-type). Note: NodeBalancer types should always be specified in lowercase. |
42
42
|`enable-ipv6-ingress`| bool |`false`| When `true`, both IPv4 and IPv6 addresses will be included in the LoadBalancerStatus ingress |
43
-
|`enable-ipv6-backends`| bool |`false`| When `true`, non-VPC NodeBalancer services use public IPv6 backend nodes. This requires a dual-stack cluster and a dual-stack Service configuration. Reconciliation fails if a selected backend node does not have public IPv6. |
43
+
|`enable-ipv6-backends`| bool |`false`| When `true`, NodeBalancer services use IPv6 backend nodes. If VPC-backed NodeBalancers are enabled, CCM preserves the NodeBalancer VPC configuration. This requires a dual-stack cluster and a dual-stack Service configuration. Reconciliation fails if a selected backend node does not have the required IPv6 address. |
44
44
|`backend-ipv4-range`| string || The IPv4 range from VPC subnet to be applied to the NodeBalancer backend. See [Nodebalancer VPC Configuration](#nodebalancer-vpc-configuration)|
45
45
|`backend-vpc-name`| string || VPC which is connected to the NodeBalancer backend. See [Nodebalancer VPC Configuration](#nodebalancer-vpc-configuration)|
46
46
|`backend-subnet-name`| string || Subnet within VPC which is connected to the NodeBalancer backend. See [Nodebalancer VPC Configuration](#nodebalancer-vpc-configuration)|
Copy file name to clipboardExpand all lines: docs/configuration/environment.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ The CCM supports the following flags:
53
53
|`--nodebalancer-backend-ipv4-subnet-name`| String |`""`| ipv4 subnet name to use for NodeBalancer backends |
54
54
|`--disable-nodebalancer-vpc-backends`| Boolean |`false`| don't use VPC specific ip-addresses for nodebalancer backend ips when running in VPC (set to `true` for backward compatibility if needed) |
55
55
|`--enable-ipv6-for-loadbalancers`| Boolean |`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. |
56
-
|`--enable-ipv6-for-nodebalancer-backends`| Boolean |`false`| Use public IPv6 addresses for non-VPC NodeBalancer service backends. This requires a dual-stack cluster and dual-stack Service configuration. If enabled, every selected backend node must have public IPv6 or reconciliation will fail. This can also be configured per-service using the `service.beta.kubernetes.io/linode-loadbalancer-enable-ipv6-backends` annotation. |
56
+
|`--enable-ipv6-for-nodebalancer-backends`| Boolean |`false`| Use IPv6 addresses for NodeBalancer service backends. If VPC-backed NodeBalancers are enabled, CCM preserves the NodeBalancer VPC configuration. Enabling this flag can migrate existing eligible NodeBalancer services from IPv4 to IPv6 backends during reconcile. This requires a dual-stack cluster and dual-stack Service configuration. If enabled, every selected backend node must have the required IPv6 address or reconciliation will fail. This can also be configured per-service using the `service.beta.kubernetes.io/linode-loadbalancer-enable-ipv6-backends` annotation. |
57
57
|`--node-cidr-mask-size-ipv4`| Int |`24`| ipv4 cidr mask size for pod cidrs allocated to nodes |
58
58
|`--node-cidr-mask-size-ipv6`| Int |`64`| ipv6 cidr mask size for pod cidrs allocated to nodes |
59
59
|`--nodebalancer-prefix`| String |`ccm`| Name prefix for NoadBalancers. |
Copy file name to clipboardExpand all lines: docs/configuration/loadbalancer.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ IPv6 frontends and IPv6 backends are configured independently. Frontend IPv6 con
50
50
51
51
IPv6 backends require a dual-stack workload cluster. In practice, the cluster networking stack must support IPv6 NodePort traffic, and the Service itself should be created as dual-stack. A single-stack IPv4 `LoadBalancer` Service can still be annotated for IPv6 backends, but the NodeBalancer health checks and traffic path may fail because the backend NodePort is not exposed over IPv6.
52
52
53
-
For newly created non-VPC NodeBalancer services, you can enable public IPv6 backends globally:
53
+
You can enable IPv6 backends globally for NodeBalancer services:
54
54
55
55
```yaml
56
56
spec:
@@ -71,13 +71,12 @@ metadata:
71
71
```
72
72
73
73
When IPv6 backends are enabled:
74
-
- only non-VPC NodeBalancer services are affected
75
-
- existing services are not migrated automatically
76
-
- every selected backend node must have public IPv6
74
+
- both VPC-backed and non-VPC-backed NodeBalancer services are affected
75
+
- when VPC-backed NodeBalancers are enabled, CCM preserves the NodeBalancer VPC configuration instead of dropping it
76
+
- enabling the global `--enable-ipv6-for-nodebalancer-backends` flag can migrate existing eligible NodeBalancer services from IPv4 to IPv6 backends during reconcile
77
+
- every selected backend node must have an IPv6 address in the currently selected backend path
77
78
- the workload cluster and Service must be configured for dual-stack networking
78
-
- reconciliation fails and CCM logs an error if a selected backend node does not have public IPv6
79
-
80
-
VPC backend behavior is unchanged and continues to use the existing IPv4/VPC backend flow.
79
+
- reconciliation fails and CCM logs an error if a selected backend node does not have the required IPv6 address
81
80
82
81
Recommended Service configuration for IPv6 backends:
0 commit comments