History

Kenichi Omichi 486b223e01 Replace kube-master with kube_control_plane (#7256 ) This replaces kube-master with kube_control_plane because of [1]: The Kubernetes project is moving away from wording that is considered offensive. A new working group WG Naming was created to track this work, and the word "master" was declared as offensive. A proposal was formalized for replacing the word "master" with "control plane". This means it should be removed from source code, documentation, and user-facing configuration from Kubernetes and its sub-projects. NOTE: The reason why this changes it to kube_control_plane not kube-control-plane is for valid group names on ansible. [1]: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint/README.md#motivation		2021-03-23 17:26:05 -07:00
..
modules/kubernetes-cluster	Terraform support for UpCloud (#7360 )	2021-03-15 01:41:04 -07:00
sample-inventory	Terraform support for UpCloud (#7360 )	2021-03-15 01:41:04 -07:00
templates	Replace kube-master with kube_control_plane (#7256 )	2021-03-23 17:26:05 -07:00
cluster-settings.tfvars	Terraform support for UpCloud (#7360 )	2021-03-15 01:41:04 -07:00
main.tf	Terraform support for UpCloud (#7360 )	2021-03-15 01:41:04 -07:00
output.tf	Terraform support for UpCloud (#7360 )	2021-03-15 01:41:04 -07:00
README.md	Terraform support for UpCloud (#7360 )	2021-03-15 01:41:04 -07:00
variables.tf	Terraform support for UpCloud (#7360 )	2021-03-15 01:41:04 -07:00
versions.tf	Terraform support for UpCloud (#7360 )	2021-03-15 01:41:04 -07:00

README.md

Kubernetes on UpCloud with Terraform

Provision a Kubernetes cluster on UpCloud using Terraform and Kubespray

Overview

The setup looks like following

   Kubernetes cluster
+-----------------------+
|   +--------------+    |
|   | +--------------+  |
|   | |              |  |
|   | | Master/etcd  |  |
|   | | node(s)      |  |
|   +-+              |  |
|     +--------------+  |
|           ^           |
|           |           |
|           v           |
|   +--------------+    |
|   | +--------------+  |
|   | |              |  |
|   | |    Worker    |  |
|   | |    node(s)   |  |
|   +-+              |  |
|     +--------------+  |
+-----------------------+

Requirements

Terraform 0.13.0 or newer

Quickstart

NOTE: Assumes you are at the root of the kubespray repo.

For authentication in your cluster you can use the environment variables.

export TF_VAR_UPCLOUD_USERNAME=username
export TF_VAR_UPCLOUD_PASSWORD=password

To allow API access to your UpCloud account, you need to allow API connections by visiting Account-page in your UpCloud Hub.

Copy the cluster configuration file.

CLUSTER=my-upcloud-cluster
cp -r inventory/sample inventory/$CLUSTER
cp contrib/terraform/upcloud/cluster-settings.tfvars inventory/$CLUSTER/
export ANSIBLE_CONFIG=ansible.cfg
cd inventory/$CLUSTER

Edit cluster-settings.tfvars to match your requirement.

Run Terraform to create the infrastructure.

terraform init ../../contrib/terraform/upcloud
terraform apply --var-file cluster-settings.tfvars \
    -state=tfstate-$CLUSTER.tfstate \
     ../../contrib/terraform/upcloud/

You should now have a inventory file named inventory.ini that you can use with kubespray. You can use the inventory file with kubespray to set up a cluster.

It is a good idea to check that you have basic SSH connectivity to the nodes. You can do that by:

ansible -i inventory.ini -m ping all

You can setup Kubernetes with kubespray using the generated inventory:

ansible-playbook -i inventory.ini ../../cluster.yml -b -v

Teardown

You can teardown your infrastructure using the following Terraform command:

terraform destroy --var-file cluster-settings.tfvars \
      -state=tfstate-$CLUSTER.tfstate \
      ../../contrib/terraform/upcloud/

Variables

hostname: A valid domain name, e.g. example.com. The maximum length is 128 characters.
template_name: The name or UUID of a base image
username: a user to access the nodes
ssh_public_keys: List of public SSH keys to install on all machines
zone: The zone where to run the cluster
machines: Machines to provision. Key of this object will be used as the name of the machine
- node_type: The role of this node (master|worker)
- cpu: number of cpu cores
- mem: memory size in MB
- disk_size: The size of the storage in GB