This tutorial will guide you through the installation of the Canonical Distribution of Kubernetes® with a few simple commands using conjure-up.
In partnership with Google, Canonical now delivers a ‘pure K8s’ experience, tested across a wide range of clouds and integrated with modern metrics and monitoring.
The Canonical Distribution of Kubernetes works across all major public clouds and private infrastructure, enabling your teams to operate Kubernetes clusters on demand, anywhere.
conjure-up lets you easily deploy and configure complex big-software solutions on public clouds, private clouds and developer laptops.
- How to install software using a conjure-up spell
- The simplest way to install The Canonical Distribution of Kubernetes
A Linux system with snapd installed
Account credentials for one of the following public cloud providers: - AWS - Azure - CloudSigma - Google - Joyent
Although this tutorial will assume a public cloud installation, if you wish to install locally the following minimum specifications are recommended: - 2 cores - 16G RAM - 32G Swap - 250G SSD with a separate block device for ZFS. Our recommendation for that device is 100G.
ⓘ Note: ZFS is recommended, but not required.
Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation
If you have not done so on your local machine, install conjure-up.
On a Linux system with snapd, we simply type the following:
sudo snap install conjure-up --classic
ⓘ Note: If you need to install snapd on your Linux system, detailed instructions can be found in the snapcraft.io documentation.
Now that we’ve installed conjure-up, let’s run it:
Next we see a list of recommended spells. From this list, select “The Canonical Distribution of Kubernetes” and press enter.
conjure-up will then ask where we would like to deploy the applications.
For this tutorial we’re going to demonstrate installation on a public cloud using Amazon AWS.
Although each cloud provider will differ slightly, the required configuration steps will generally include choosing a region and providing credentials.
Now that we have configured our cloud provider, we’re presented with a screen titled “CHOOSE A CONTROLLER OR CREATE NEW”.
For the purposes of this tutorial we’ll start from scratch and select “Deploy New Self-Hosted Controller”.
We will now see a list of the applications required for a Kubernetes installation. Each application can be configured individually, but for now, let’s select “Deploy all remaining applications” to use the suggested default configuration.
You’ll see verbose output as machines are automatically provisioned and the Kubernetes cluster components are installed and configured.
Check the box to install the applications and enter your sudo password when prompted.
Congratulations, you have installed and configured a cluster running the Canonical Distribution of Kubernetes.
Now that you have your cluster, you can put it to work:
- The easy way to commoditise GPUs for Kubernetes
- Build a transcoding platform in minutes
- Transform your solution into a private PaaS