56190fb314
The script had a typo that prevents it from running on a brand new host, this commit fixes that. Change-Id: If73bfcbed5adc703c256c02dcb90a71f6b713a74
Kubeadm AIO Container
This container builds a small AIO Kubeadm based Kubernetes deployment for Development and Gating use.
Instructions
OS Specific Host setup:
Ubuntu:
From a freshly provisioned Ubuntu 16.04 LTS host run:
sudo apt-get update -y
sudo apt-get install -y \
docker.io \
nfs-common
Build and deploy the AIO environment
From the root directory of the OpenStack-Helm repo run:
export KUBEADM_IMAGE=openstack-helm/kubeadm-aio:v1.6
sudo docker build --pull -t ${KUBEADM_IMAGE} tools/kubeadm-aio
To launch the environment then run:
export KUBEADM_IMAGE=openstack-helm/kubeadm-aio:v1.6
export KUBE_VERSION=v1.6.0
./tools/kubeadm-aio/kubeadm-aio-launcher.sh
export KUBECONFIG=${HOME}/.kubeadm-aio/admin.conf
One this has run, you should hopefully have a Kubernetes single node environment running, with Helm, Calico, a NFS PVC provisioner and appropriate RBAC rules and node labels to get developing.
If you wish to use this environment at the primary Kubernetes environment on your host you may run the following, but note that this will wipe any previous client configuration you may have.
mkdir -p ${HOME}/.kube
cat ${HOME}/.kubeadm-aio/admin.conf > ${HOME}/.kube/config
If you wish to create dummy network devices for Neutron to manage there is a helper script that can set them up for you:
sudo docker exec kubelet /usr/bin/openstack-helm-aio-network-prep
Logs
You can get the logs from your kubeadm-aio container by running:
sudo docker logs -f kubeadm-aio