Kind: DualStack UX

Created on 22 Jan 2020  Â·  13Comments  Â·  Source: kubernetes-sigs/kind

What would you like to be added:

The more we dig into dual-stack with kubernetes the more doubts it generates, instead of implementing blindly I'd like first to define a good UX from KIND perspective.
At least, we should define the API so it covers most of the use cases.

Why is this needed:

DualStack clusters can have several combinations based on the following parameters:

  • podSubnets
  • serviceSubnets
  • IPv6DualStack featureGate

The first subnet determines the default family of the cluster for dual-stack clusters.

Based on that the cluster can be:

  • ipv4 only
  • ipv6 only
  • ipv4 only with dual-stack enabled
  • ipv6 only with dual-stack enabled
  • dual stack and ipv4 default
  • dual stack and ipv6 default

How should we define the API?

networking:
  ipfamily: ipv4ipv6-dualstack # or whatever we want to call this
kindesign kinexternal kinfeature lifecyclfrozen prioritimportant-longterm

Most helpful comment

Dual Stack KEP is going to be updated soon, as soon as it's clearly defined the next steps will update the issue

All 13 comments

/cc @mauilion @BenTheElder

We definitely want to track upstream closely, it seems currently the APIs there need some rethinking..

/kind design

adding external label until upstream seems settled 🙃

Any update on this?

last I checked in upstream was still struggling with this, when upstream is
ready we'll do our best to follow.

On Tue, Apr 7, 2020 at 2:10 PM Manuel Alejandro de Brito Fontes <
[email protected]> wrote:

Any update on this?

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/kind/issues/1275#issuecomment-610622326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHADKZWJB6LVBZTFCUXFELRLOJDRANCNFSM4KKIABVA
.

Dual Stack KEP is going to be updated soon, as soon as it's clearly defined the next steps will update the issue

We should PR kubelet upstream to allow setting multiple node IPs natively.

There are two prevailing thoughts (rest is mechanics). Services are single stack by default (if user want to different default, they should use webhooks). Dualstack is set to be preferred or required depending on how the api is expressed. Sorry it is taking time. promise we code fast once we get the kep agreed upon.

No worries, it will be good to get this right :-)

Thanks for the update!

On Wed, Jun 10, 2020 at 5:30 PM Khaled Henidak (Kal) <
[email protected]> wrote:

There are two prevailing thoughts (rest is mechanics). Services are single
stack by default (if user want to different default, they should use
webhooks). Dualstack is set to be preferred or required depending on how
the api is expressed. Sorry it is taking time. promise we code fast once we
get the kep agreed upon.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/kind/issues/1275#issuecomment-642335958,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHADK6YTEWK33OE6X2KKWDRWAQR7ANCNFSM4KKIABVA
.

@BenTheElder time unfreeze this :-)

I've been reviewing the PR!

On Wed, Nov 4, 2020 at 12:40 PM Khaled Henidak (Kal) <
[email protected]> wrote:

@BenTheElder https://github.com/BenTheElder time unfreeze this :-)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/kind/issues/1275#issuecomment-721963379,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHADK3EXKLC6TYLENXAEM3SOG34LANCNFSM4KKIABVA
.

Was this page helpful?
0 / 5 - 0 ratings