Skip to content

KEP-1880: updating KEP #3844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Feb 7, 2023
Merged

KEP-1880: updating KEP #3844

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
1de6e91
update kep metadata
aojea Feb 6, 2023
d7560d9
update questionary
aojea Feb 6, 2023
2232222
Replace API name ServiceCIDRConfig by ServiceCIDR
aojea Feb 6, 2023
b8c970d
be compatible with current service IP reservation
aojea Feb 6, 2023
8af5e86
update test plan
aojea Feb 6, 2023
0e02167
define number of controllers required
aojea Feb 6, 2023
756f008
bootstrap process
aojea Feb 6, 2023
d319cec
address comments
aojea Feb 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions keps/sig-network/1880-multiple-service-cidrs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -252,13 +252,11 @@ multiple apiservers.

The new allocation mode requires:

- 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.
- 1 new allocator implementing current `allocator.Interface`, that runs in each apiserver, and uses the new objects to allocate IPs for Services.
- 1 new controller that participates on the ServiceCIDR deletion, the guarantee that each IPAddresses has
a ServiceCIDR associated. It also handles the special case for the `default` ServiceCIDR.
- 1 new controller that participates in the IPAddress deletion, that guarantees that each Service IP
allocated has its corresponding IPAddress object, recreating it if necessary.
- 1 new controller that handles the bootstrap process and the default ServiceCIDR.
- 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.
- 1 new allocator implementing current `allocator.Interface`, that runs in each apiserver, and uses the new ServiceCIDRs objects to allocate IPs for Services.
- 1 new repair loop that runs in the apiserver that reconciles the Services with the IPAddresses, repairing
Services, garbage collecting orphan IPAddresses and handling the upgrade from the old allocators.
- 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.

[![](https://mermaid.ink/img/pako:eNp9UstqwzAQ_BWxx5IcCqUHUwrFacGXYJLeqh620tpV0SNIcsAk_vfKjpNiJ3QvYmdGs7NIBxBOEmQgNIawUlh7NNyyVAPCtuT3StDhhPWV6yZE8kXJQvTK1jeYwD4-52RRvqFRWlFPjk17Rbel00q07G7av7c7Omm7G-HyYrXJna1UfYm5RkOzfEW5f7iGHifQxL0oX6T0FMJ_rhuqmPv6ScfE4VynbszJONxzYE_H5fL4PDaXIVkCUGsnMFLgMLn4t-DcYj23EM5GVHZwgAUY8gaVTA88LMEhfpMhDr1UUoWNjr2yS9JmJ9PoV6mi85BVqAMtAJvotq0VkEXf0Fk0_pNR1f0CyVS2dw)](https://mermaid.live/edit#pako:eNp9UstqwzAQ_BWxx5IcCqUHUwrFacGXYJLeqh620tpV0SNIcsAk_vfKjpNiJ3QvYmdGs7NIBxBOEmQgNIawUlh7NNyyVAPCtuT3StDhhPWV6yZE8kXJQvTK1jeYwD4-52RRvqFRWlFPjk17Rbel00q07G7av7c7Omm7G-HyYrXJna1UfYm5RkOzfEW5f7iGHifQxL0oX6T0FMJ_rhuqmPv6ScfE4VynbszJONxzYE_H5fL4PDaXIVkCUGsnMFLgMLn4t-DcYj23EM5GVHZwgAUY8gaVTA88LMEhfpMhDr1UUoWNjr2yS9JmJ9PoV6mi85BVqAMtAJvotq0VkEXf0Fk0_pNR1f0CyVS2dw)

Expand Down