gregandev
/
k3d
mirror of https://github.com/k3d-io/k3d
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Little helper to run CNCF's k3s in Docker
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
568 Commits
25 Branches
165 Tags
70 MiB
 
 
 
 
Tag: Branch: Tree: 2d6a67822c
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2d6a67822c'
${ noResults }
k3d/docs/internals/networking.md

1.0 KiB
Raw Blame History

Networking

Introduction

By default, k3d creates a new (docker) network for every new cluster. Using the --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

host network

When using the --network flag to connect to the host network (i.e. k3d create cluster --network host), you won't be able to create more than one master node. An edge case would be one master node (with agent disabled) and one worker node.

bridge network

By default, every network that k3d creates is working in bridge mode. 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.

none "network"

Well.. this doesn't really make sense for k3d anyway ¯_(ツ)_/¯