Skip to content

Commit c6e3693

Browse files
authored
Merge pull request #4253 from aojea/cluster_cidr
KEP 2593: withdrawn cluster-cidr kep
2 parents 2d97fc0 + 19decda commit c6e3693

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

keps/sig-network/2593-multiple-cluster-cidrs/README.md

+5
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,11 @@ release*.
100100

101101
## Summary
102102

103+
104+
IMPORTANT: THIS KEP HAS BEEN WITHDRAWN AND THIS FEATURE WILL BE DEVELOPED OUT OF TREE
105+
Ref: https://groups.google.com/g/kubernetes-sig-network/c/nts1xEZ--gQ/m/2aTOUNFFAAAJ
106+
107+
103108
Today, when Kubernetes' NodeIPAM controller allocates IP ranges for podCIDRs for
104109
nodes, it uses a single range allocated to the cluster (cluster CIDR). Each node
105110
gets a range of a fixed size from the overall cluster CIDR. The size is

keps/sig-network/2593-multiple-cluster-cidrs/kep.yaml

+2-5
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ authors:
44
- "@rahulkjoshi"
55
- "@sdmodi"
66
owning-sig: sig-network
7-
status: implementable
7+
status: withdrawn
88
creation-date: 2021-03-22
99
reviewers:
1010
- "@mskrocki"
@@ -18,13 +18,10 @@ stage: beta
1818
# The most recent milestone for which work toward delivery of this KEP has been
1919
# done. This can be the current (upcoming) milestone, if it is being actively
2020
# worked on.
21-
latest-milestone: "v1.27"
21+
latest-milestone: "v1.29"
2222

2323
# The milestone at which this feature was, or is targeted to be, at each stage.
2424
milestone:
25-
alpha: "v1.25"
26-
beta: "v1.27"
27-
stable: "v1.29"
2825

2926
feature-gates:
3027
- name: MultiCIDRRangeAllocator

0 commit comments

Comments
 (0)