Skip to content

Deploy k8s on OpenStack via Ansible (with kube-router but without open-stack cloud provider)

License

Notifications You must be signed in to change notification settings

pfisterer/k8s-ansible-openstack

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

k8s-on-openstack

This is a modified version of infraly/k8s-on-openstack. In contrast to the previous playbook, this modified version

  • does NOT use a Kubernetes' OpenStack cloud provider but
  • does deploy Kubernetes on an OpenStack cluster using Ansible and with kube-router.

The rationale behind this decision is that in some OpenStack deployments, the virtual machines are - for security reasons - not allowed to connect to OpenStack.

It is based on the following tools:

Todos

  • Use kube-router again
  • Storage allocation for PVCs, etc.
  • Verify that networking and direct server return works
  • Reverse ingress proxy

Prerequisites

  • Ansible (tested with version 2.4)
  • Shade library required by Ansible OpenStack modules (python-shade for Debian, pip install shade otherwise)

Getting started

The following mandatory environment variables need to be set before calling ansible-playbook:

  • OS_*: standard OpenStack environment variables such as OS_AUTH_URL, OS_USERNAME, ...
  • KEY: name of an existing SSH keypair

The following optional environment variables can also be set:

  • NAME: name of the Kubernetes cluster, used to derive instance names, kubectl configuration and security group name
  • IMAGE: name of an existing Ubuntu 16.04 image
  • NETWORK: name of the network to which instances should be connected
  • EXTERNAL_NETWORK: name of the neutron external network, defaults to 'public'
  • FLOATING_IP_POOL: name of the floating IP pool
  • FLOATING_IP_NETWORK_UUID: uuid of the floating IP network (required for LBaaSv2)
  • NODE_MEMORY: how many MB of memory should nodes have, defaults to 4GB
  • NODE_COUNT: how many nodes should we provision, defaults to 3
  • MASTER_BOOT_FROM_VOLUME: boot the master instance on a volume for data persistence, defaults to True
  • MASTER_TERMINATE_VOLUME: delete the volume when master instance is destroy, defaults to True
  • MASTER_VOLUME_SIZE: size of the master volume
  • MASTER_MEMORY: how many MB of memory should master have, defaults to 4 GB
  • CLOUD_INIT_APT_EXTRA_CONFIG: extra configuration options for apt via cloud init (e.g., to use an proxy for apt: export CLOUD_INIT_APT_EXTRA_CONFIG="http_proxy: http://1.2.3.4:3142/")

Spin up a new cluster:

ansible-playbook site.yaml

Destroy the cluster:

ansible-playbook destroy.yaml

Generated files:

Verify its working:

kubectl run source-ip-app --image=k8s.gcr.io/echoserver:1.4

# Cluster IP
kubectl expose deployment source-ip-app --name=clusterip --port=80 --target-port=8080
kubectl get svc clusterip
kubectl run busybox -it --image=busybox --restart=Never --rm
wget -qO - <put the cluster ip here>

# Node Port
kubectl expose deployment source-ip-app --name=nodeport --port=80 --target-port=8080 --type=NodePort
NODEPORT=$(kubectl get -o jsonpath="{.spec.ports[0].nodePort}" services nodeport)
curl http://<external public ip of the master node>:$NODEPORT

Authors

About

Deploy k8s on OpenStack via Ansible (with kube-router but without open-stack cloud provider)

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages