Note that down
only works well if the variables defined before the invocation
of the script are similar to the variables defined before invoking the up
command.
# create box
PROJECT=xperiment ./01-setup-control.mech up
# destroy box
PROJECT=xperiment ./01-setup-control.mech down
LOCAL_PORT=4002 USER=david TUNNEL_HOST=CONTROLLER_EXTERNAL_IP ./02-setup-ssh-tunnels.sh up
Defining TUNNEL_HOST
will tunnel the connection through the specified
machine. Unless the REMOTE_HOST
is specified, the tunnel will patch us
through to the REMOTE_HOST
which by default contains the loopback
address therefore patching us through to the tunnel host itself 😉.
LOCAL_PORT=4002 USER=david TUNNEL_HOST=CONTROLLER_EXTERNAL_IP ./02-setup-ssh-tunnels.sh down
In order to supply the flannel subnet manager its proper configuration, one has to describe the setup in etcd.
CONTROL_HOST=CONTROLLER_EXTERNAL_IP MASK=10.X.0.0/16 ./03-config-flannel.sh up
CONTROL_IP=CONTROLLER_INTERNAL_IP NODES="mercury venus earth mars" ./04-setup-nodes.sh up
Kubernetes requires a few services to start doing it's stuff. Provided that
the tunnel is up for fleetctl
to do her work one may setup the
Kubernetosphere.
CONTROL_IP=CONTROLLER_INTERNAL_IP ./05-spawn-kubernetes-services.sh up
DNS_SERVER_IP=? DNS_REPLICAS=1 DNS_DOMAIN=example.com spawn-skydns.sh up
LOCATION=EU NAME=example.port.rotterdam ./05-create-registry-storage.sh up