| This project is experimental and should not be used in production environments. |
|---|
This Terraform module creates a Kubernetes Cluster on Linode Cloud infrastructure running Ubuntu. The cluster is designed to take advantage of the Linode regional private network, and is equiped with Linode specific cluster enhancements.
Cluster size and instance types are configurable through Terraform variables.
| k8s_version | docker_version | cni_version | crictl_version | k8s_feature_gates |
|---|---|---|---|---|
| v1.19.6 | 19.03 | v0.8.7 | v1.15.0 | |
| v1.18.13 | 19.03 | v0.8.7 | v1.15.0 | |
| v1.17.16 | 19.03 | v0.8.7 | v1.15.0 | |
| v1.16.15 | 19.03 | v0.8.7 | v1.15.0 |
- Terraform must be installed
- Bash must be installed
- SSH should be installed and configured with an SSH Key and Agent (Recommended)
- Having kubectl installed is recommended
Note that you'll need Terraform v0.10 or newer to run this project.
Before running the project you'll have to create an access token for Terraform to connect to the Linode API.
Using the token and your access key, create the LINODE_TOKEN environment variable:
read -sp "Linode Token: " TF_VAR_linode_token # Enter your Linode Token (it will be hidden)
export TF_VAR_linode_tokenThis variable will need to be supplied to every Terraform apply, plan, and destroy command using -var linode_token=$LINODE_TOKEN unless a terraform.tfvars file is created with this secret token.
Create a main.tf file in a new directory with the following contents:
module "k8s" {
source = "linode/k8s/linode"
linode_token = "YOUR TOKEN HERE"
}That's all it takes to get started!
Pin to a specific module version using version = "..." to avoid upgrading to a version with breaking changes. Upgrades to this module could potentially replace all master and worker nodes resulting in data loss. The terraform plan will report this, but it may not be obvious.
module "k8s" {
source = "linode/k8s/linode"
version = "0.1.0"
linode_token = "YOUR TOKEN HERE"
}Choose a Terraform workspace name (because the default is default). In this example we've chosen linode. The workspace name will be used as a prefix for Linode resource created in this cluster, for example: linode-master-1, linode-node-1. Alternate workspaces can be created and selected to change clusters.
terraform workspace new linodeCreate an Linode Kubernetes cluster with one master and a node:
terraform apply \
-var region=eu-west \
-var server_type_master=g6-standard-2 \
-var nodes=1 \
-var server_type_node=g6-standard-2 \This will do the following:
- provisions Linode Instances in parallel with Ubuntu 20.04 (the Linode instance type/size of the
masterand thenodemay be different) - connects to the Linode Instances via SSH and installs various Kubernetes components and supporting binaries: kubeadm, kubectl, kubelet, kubernetes-cni, and crictl.
- installs a Calico network between Linode Instances
- runs kubeadm init on the master server and configures kubectl
- joins the nodes in the cluster using the kubeadm token obtained from the master
- installs Linode add-ons:
- CSI (LinodeBlock Storage Volumes)
- CCM (Linode NodeBalancers)
- External-DNS (Linode Domains)
- installs cluster add-ons:
- installs Linode add-ons:
- copies the kubectl admin config file for local
kubectluse via the public IP of the API server
A full list of the supported variables are available in the Terraform Module Registry.
After applying the Terraform plan you'll see several output variables like the master public IP,
the kubeadmn join command and the current workspace admin config (for use with kubectl).
The cluster node count can be scaled up by increasing the number of Linode Instances acting as nodes:
terraform apply -var nodes=3Tear down the whole infrastructure with:
terraform destroy -forceBe sure to clean-up any CSI created Block Storage Volumes, and CCM created NodeBalancers that you no longer require.
The kubectl config file format is <WORKSPACE>.conf as in linode.conf. Kubectl will use this file when provided through --kubeconfig or when set in the KUBECONFIG environment variable.
If you have kubectl install locally, you can use it to work with your Linode cluster. You can always ssh into the master Linode Instance and run kubectl there (without the --kubeconfig option or environment variable).
$ export KUBECONFIG="$(pwd)/$(terraform output kubectl_config)"
$ kubectl top nodes
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
linode-master-1 655m 16% 873Mi 45%
linode-node-1 147m 3% 618Mi 32%
linode-node-2 101m 2% 584Mi 30%In order to access the dashboard locally, you can use kubectl proxy then browse to http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy
$ kubectl proxy &
[1] 37630
Starting to serve on 127.0.0.1:8001To authenticate, provide the kubeconfig file or generate a token. For demonstrative purposes, an existing system token can be used. This is not recommended for production clusters.
kubectl -n kube-system describe secrets `kubectl -n kube-system get secrets | awk '/clusterrole-aggregation-controller/ {print $1}'` | awk '/token:/ {print $2}'
A primary function of the CCM is to register and maintain Kubernetes LoadBalancer settings within a Linode NodeBalancer. This is needed to allow traffic from the Internet into the cluster in the most fault tollerant way (obviously very important!)
The CCM also annotates new Kubernetes Nodes with Linode specific details, including the LinodeID and instance type. Linode hostnames and network addresses are automatically associated with their corresponding Kubernetes resources, forming the basis for a variety of Kubernetes features.
The CCM monitors the Linode API for changes in the Linode instance and will remove a Kubernetes Node if it finds the Linode has been deleted. Resources will automatically be re-scheduled if the Linode is powered off.
Learn more about the CCM concept on kubernetes.io.
The CSI provides a Kubernetes Storage Class which can be used to create Persistent Volumes (PV) using Linode Block Storage Volumes. Pods then create Persistent Volume Claims (PVC) to attach to these volumes.
When a PV is deleted, the Linode Block Storage Volume will be deleted as well, based on the ReclaimPolicy.
In this Terraform Module, the DefaultStorageClass is provided by the Linode CSI. Persistent volumes can be defined with an alternate storageClass.
Learn More about Persistent Volumes on kubernetes.io.
Unlike CoreDNS (or KubeDNS), which provides DNS services within the Kubernetes cluster, External-DNS publishes the public facing IP addresses associated with exposed services to a public DNS server, such as the Linode DNS Manager.
As configured in this Terraform module, any service or ingress with a specific annotation, will have a DNS record managed for it, pointing to the appropriate Linode or NodeBalancer IP address. The domain must already be configured in the Linode DNS Manager.
Learn more at the External-DNS Github project.
To make changes to this project, verify that you have the prerequisites and then clone the repo. Instead of using the Terraform module syntax, and being confined by the variables that are provided, you'll be able to make any changes necessary.
git clone https://github.com/linode/terraform-linode-k8s.git
cd terraform-linode-k8sOr if you won't be submitting changes, you can use terraform init:
terraform init --from-module=linode/k8s/linode linode-k8sThis terraform modules is composed of three sub-modules for reuse and separation of concerns.
- Instance - Provisions a base Linode Instance for the cluster.
- Master - Uses the Instance module as a base and futher provisions a Kubernetes control-plane.
- Node - Uses the Instance module as a base and further provisions a Kubernetes worker joined to a control-plane using module parameters.
Would you like to improve the terraform-linode-k8s module? Please start here.
For general help or discussion, join the Kubernetes Slack channel #linode.