In this tutorial you are going to learn how to create a second production cluster (e.g. to have a fallback or to migrate to a different cloud provider) for your E-Commerce team.
We have already set up a project for the production clusters of this team, let’s take a look at it.
This project configuration will match every production cluster of our E-Commerce team; Let’s give them admin access to the cluster. For this we need an admin role, which we will define as the permission to do everything on the cluster:
We can now attach the role to a policy for this cluster and give all developers access. We defined the developer group under Administration > Access Control > Group before.
The E-Commerce backend our team will be using needs some environment variables, we will configure them through a config map.
The backend also needs access to our AWS S3 Bucket and to GitHub, so we create two secrets for this:
Getting a second production cluster
This project currently only has one cluster attached to it, now we want to create a second cluster. To provision another cluster on AWS we first need to setup our cloud provider. To do this we need to visit Administration > Cloud Providers and click the Add button. We need to put our AWS credentials into the form and save the cloud provider.
Once we did this we can go to the clusters view, click the Add Cluster button and select Create Konvoy Cluster.
It’s important that we set the right labels for our cluster, but not to worry, you can still change them after the cluster is created.
After the cluster is created we can download the kubeconfig file for this cluster and take a look at what we have created.
To do this we need to install
kubectl on our machine and set the
KUBECONFIG environment variable to an absolute path to our downloaded kubeconfig file.
As the cluster has labels matching our E-Commerce Production Project the resources defined there are automatically provisioned to the cluster, so we are done creating a second prodiction cluster.