mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-04-27 00:58:13 -04:00
7a9bca3888
When MultiCIDRServiceAllocator feature is enabled, we added an additional feature gate DisableAllocatorDualWrite that allows to enable a mirror behavior on the old allocator to deal with problems during cluster upgrades. During the implementation the secondary range of the legacy allocator was initialized with the valuye of the primary range, hence, when a Service tried to allocate a new IP on the secondary range, it succeded in the new ip allocator but failed when it tried to allocate the same IP on the legacy allocator, since it has a different range. Expand the integration test that run over all the combinations of Service ClusterIP possibilities to run with all the possible combinations of the feature gates. The integration test need to change the way of starting the apiserver otherwise it will timeout. |
||
|---|---|---|
| .. | ||
| admissionregistration | ||
| apiserverinternal | ||
| apps | ||
| authentication | ||
| authorization | ||
| autoscaling | ||
| batch | ||
| certificates | ||
| coordination | ||
| core | ||
| discovery | ||
| events | ||
| flowcontrol | ||
| networking | ||
| node | ||
| policy | ||
| rbac | ||
| registrytest | ||
| resource | ||
| scheduling | ||
| storage | ||
| storagemigration | ||
| doc.go | ||
| OWNERS | ||