This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 193
Dual-stack support on vSphere #616
Labels
Milestone
Comments
5 tasks
5 tasks
5 tasks
This was referenced Oct 19, 2021
3 tasks
3 tasks
3 tasks
10 tasks
All known items that we think need to be done for dual-stack have been done and dual-stack support has been added. Closing issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the feature request
As an admin/operator:
I would like to be able to configure/deploy Kubernetes clusters that support dual stack networking (IPv4/IPv6)
Because:
The routing of workload traffic, both ingress and egress, may be conditional on the type of workload, and thus may also select a specific address family (IPv4 or IPv6) based on the workload type. Therefore we want to configure/deploy Kubernetes clusters that support dual-stack traffic, both ingress and egress.
Proposal
An admin/operator can specify
ipv4,ipv6
oripv6,ipv4
for theTKG_IP_FAMILY
field. The first IP family in the list becomes the "primary" ip family of the cluster. This matters in various ways e.g SingleStack Services, defaultpodIP
, upgrading from a single stack to dual-stack, control plane endpoint VIP.If specified, the
SERVICE_CIDR
andCLUSTER_CIDR
must be a list of two CIDRs and must match the order ofTKG_IP_FAMILY
.If
SERVICE_CIDR
orCLUSTER_CIDR
is not specified it should default to the defaultipv4
andipv6
CIDRs in the correct order.Describe alternatives you've considered
n/a
Affected product area (please put an X in all that apply)
Additional context
cc @mcwumbly @tylerschultz @adobley
The text was updated successfully, but these errors were encountered: