You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
I would like for it to be considered for the built-in providers (docker, podman, nerdctl) to provision the nodes with an additional label, perhaps in the format io.x-k8s.kind.network=<networkName>
Why is this needed:
Acknowledging that env variable KIND_EXPERIMENTAL_DOCKER_NETWORK is taken into account during cluster creation for setting the provider network each node is connected to, AND that it is an experimental flag at that, adding this label lays the foundation for a further enhancement to cloud-provider-kind allowing the spawned loadbalancer nodes to be properly connected to the same network as the cluster they are serving.
I have a branch ready for PR if things are amenable: TrooperT/kind
The text was updated successfully, but these errors were encountered:
What would you like to be added:
I would like for it to be considered for the built-in providers (docker, podman, nerdctl) to provision the nodes with an additional label, perhaps in the format
io.x-k8s.kind.network=<networkName>
Why is this needed:
Acknowledging that env variable
KIND_EXPERIMENTAL_DOCKER_NETWORK
is taken into account during cluster creation for setting the provider network each node is connected to, AND that it is an experimental flag at that, adding this label lays the foundation for a further enhancement to cloud-provider-kind allowing the spawned loadbalancer nodes to be properly connected to the same network as the cluster they are serving.I have a branch ready for PR if things are amenable: TrooperT/kind
The text was updated successfully, but these errors were encountered: