- Related issues:
By default, k3d creates a new (docker) network for every new cluster.
--network STRING flag upon creation to connect to an existing network.
Existing networks won’t be managed by k3d together with the cluster lifecycle.
Connecting to docker “internal”/pre-defined networks¶
When using the
--network flag to connect to the host network (i.e.
k3d cluster create --network host), you won’t be able to create more than one server node.
An edge case would be one server node (with agent disabled) and one agent node.
By default, every network that k3d creates is working in
But when you try to use
--network bridge to connect to docker’s internal
bridge network, you may run into issues with grabbing certificates from the API-Server.
Single-Node clusters should work though.
Well.. this doesn’t really make sense for k3d anyway ¯\_(ツ)_/¯