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
There is no need to handle the IPAddresses with finalizers since
the apiserver only deallocates the IP after the Services has been
deleted.
The repair loop on the apiserver will guarantee the relaton between
ServiceCIDR, Services and ClusterIP, there is no need to add a new
controller on the controller manager.
Copy file name to clipboardExpand all lines: keps/sig-network/1880-multiple-service-cidrs/README.md
+5-7Lines changed: 5 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -252,13 +252,11 @@ multiple apiservers.
252
252
253
253
The new allocation mode requires:
254
254
255
-
- 2 new API objects ServiceCIDR and IPAddress in networking.k8s.io/v1alpha1, see <https://groups.google.com/g/kubernetes-sig-api-machinery/c/S0KuN_PJYXY/m/573BLOo4EAAJ>. Both will be protected with finalizers.
256
-
- 1 new allocator implementing current `allocator.Interface`, that runs in each apiserver, and uses the new objects to allocate IPs for Services.
257
-
- 1 new controller that participates on the ServiceCIDR deletion, the guarantee that each IPAddresses has
258
-
a ServiceCIDR associated. It also handles the special case for the `default` ServiceCIDR.
259
-
- 1 new controller that participates in the IPAddress deletion, that guarantees that each Service IP
260
-
allocated has its corresponding IPAddress object, recreating it if necessary.
261
-
- 1 new controller that handles the bootstrap process and the default ServiceCIDR.
255
+
- 2 new API objects ServiceCIDR and IPAddress in networking.k8s.io/v1alpha1, see <https://groups.google.com/g/kubernetes-sig-api-machinery/c/S0KuN_PJYXY/m/573BLOo4EAAJ>. The ServiceCIDR will be protected with a finalizer, the IPAddress object doesn't need a finalizer because the APIserver always release and delete the IPAddress after the Service has been deleted.
256
+
- 1 new allocator implementing current `allocator.Interface`, that runs in each apiserver, and uses the new ServiceCIDRs objects to allocate IPs for Services.
257
+
- 1 new repair loop that runs in the apiserver that reconciles the Services with the IPAddresses, repairing
258
+
Services, garbage collecting orphan IPAddresses and handling the upgrade from the old allocators.
259
+
- 1 new controller that handles the bootstrap process and the ServiceCIDR object, it participates on the ServiceCIDR deletion, the guarantee that each IPAddresses has a ServiceCIDR associated.
0 commit comments