Introduction
The DKP bootstrap is created on the operator machine which utilizes both 172.18.0.0/16 as subnet and 172.18.0.1 as its gateway. If there is a conflict within the network, these values may be changed to reflect different values.
Pre-bootstrap Creation
If you have not yet ran the dkp create bootstrap command, you may pre-create the bootstrap network by doing the steps below. Change the values of the export for both SUBNET and GATEWAY accordingly.
export SUBNET=173.15.0.0/16
export GATEWAY=173.15.0.1
docker network create \
--driver bridge \
--subnet ${SUBNET} \
--gateway ${GATEWAY} \
--opt com.docker.network.bridge.enable_ip_masquerade=true \
--opt com.docker.network.driver.mtu=1500 \
--scope=local \
--ipam-driver=default \
kind
Create the bootstrap cluster
dkp create bootstrap
Verify the IP address assigned to the bootstrap cluster
$ docker ps
b6eca7751bf6 mesosphere/konvoy-bootstrap:v2.2.0-rc.7 "/usr/local/bin/entr…" 2 minutes ago Up 2 minutes 127.0.0.1:35455->6443/tcp
$ docker inspect b6eca7751bf6 | grep -i ipaddress
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "173.15.0.2",
Failed Bootstrap Creation
If you have proceeded with the steps and is left with a bootstrap cluster failing to deploy, perform the following steps to clean up the created assets.
Delete running bootstrap (if applicable)
dkp delete bootstrap
List existing docker network values
$ docker network ls
NETWORK ID NAME DRIVER SCOPE
d3889877e0ed bridge bridge local
362854d28426 host host local
8976d5db2789 kind bridge local
f8b82f095efa none null local
Delete the kind network
docker network rm kind
You may then proceed to the steps above to pre-create the bootstrap network.