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: README.md
+8-1
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,8 @@ The `kube-vip-cloud-provider` will only implement the `loadBalancer` functionali
19
19
- Setting the special IP `0.0.0.0` for DHCP workflow.
20
20
- Support single stack IPv6 or IPv4
21
21
- Support for dualstack via the annotation: `kube-vip.io/loadbalancerIPs: 192.168.10.10,2001:db8::1`
22
-
- Support ascending and descending search order by setting search-order=desc
22
+
- Support ascending and descending search order when allocating IP from pool or range by setting search-order=desc
23
+
- Support loadbalancerClass `kube-vip.io/kube-vip-class`
23
24
24
25
## Installing the `kube-vip-cloud-provider`
25
26
@@ -134,6 +135,12 @@ address in each of both IP families for the pool.
134
135
135
136
Set the CIDR to `0.0.0.0/32`, that will make the controller to give all _LoadBalancers_ the IP `0.0.0.0`.
136
137
138
+
139
+
## LoadbalancerClass support
140
+
141
+
If users only want kube-vip-cloud-provider to allocate ip for specific set of services, they can pass `KUBEVIP_ENABLE_LOADBALANCERCLASS: true` as an environment variable to kube-vip-cloud-provider. kube-vip-cloud-provider will only allocate ip to service with `spec.loadBalancerClass: kube-vip.io/kube-vip-class`.
142
+
143
+
137
144
## Debugging
138
145
139
146
The logs for the cloud-provider controller can be viewed with the following command:
klog.Warningf("service.Spec.LoadBalancerIP is defined but annotations '%s' is not, assume it's a legacy service, updates its annotations", loadbalancerIPsAnnotations)
98
98
// assume it's legacy service, need to update the annotation.
0 commit comments