In order to use the Corda Kubernetes Deployment, you will need to have the necessary platform on which to deploy. This comes in the shape of a Kubernetes cluster and Container registry, but also should have persistent storage set up. Next are some instructions on how to set up the infrastructure. Setting up the relevant cloud services is currently left to the reader, this may change in future versions of the scripts to be more automated.
These are the services you will need to have set up in order to execute the deployment scripts correctly using Microsoft Azure.
This is the main Kubernetes cluster that we will be using. Setting up the AKS will also set up a NodePool resource group. The NodePool should also have a few public IP addresses configured as Front End IP addresses for the AKS cluster.
A good guide to follow for setting up AKS: Quickstart: Deploy an Azure Kubernetes Service cluster using the Azure CLI.
Worth reading the ACR section at the same time to combine the knowledge and setup process.
The ACR provides the Docker images for the AKS to use. Please make sure that the AKS can connect to the ACR using appropriate Service Principals. See: Azure Container Registry authentication with service principals.
Guide for setting up ACR: Tutorial: Deploy and use Azure Container Registry.
Guide for connecting ACR and AKS: Authenticate with Azure Container Registry from Azure Kubernetes Service.
Worth reading the AKS section at the same time to combine the knowledge and setup process.
Service Principals is Azures way of delegating permissions between different services within Azure. There should be at least one Service Principal for AKS which can access ACR to pull the Docker images from there.
Here is a guide to get your started on SPs: Service principals with Azure Kubernetes Service (AKS).
In addition to that there should be a storage account that will host the persistent volumes (File storage).
Guide on setting up Storage Accounts: Create an Azure Storage account.
You should have a few static public IP addresses available for each deployment. One for the Node to accept incoming RPC connections from an UI level and another one if running the Float component within the cluster, this would then be the public IP address that other nodes would see and connect to.
A guide on setting up Public IP addresses in Azure: Create, change, or delete a public IP address.
These are the services you will need to have set up in order to execute the deployment scripts correctly using Amazon Web Services.
Amazon EKS is the Kubernetes cluster on AWS.
Here is a nice guide on setting up an EKS Creating an Amazon EKS cluster.
You will need to create a VPC and IAM role for this to work, but the guide describes it quite well.
We will need to set one up along with a node group (node pool), Guide on node group setup.
The ECR is the container registry, and it is required in order to host our custom built Docker images. Creating a Repository.
In addition to creating this ECR, you will have to remember to set the containerRegistry.username as "AWS" in the values.yaml file in the helm sub folder.
The way Amazon handles persistent storage for Kubernetes clusters is by way of EBS. We will have to provision some EBS volumes and dedicate a host for them. In order to set them up we should start by following this guide: EC2 + EBS volumes.
Please make sure you create at least the following:
- 1Gb EBS volume for the Float component
- 1Gb EBS volume for the Bridge component
- 2Gb EBS volume for the Node
The volumes have to be assigned to a specific host, and that host also has to be specified in the values.yaml file in the helm sub folder later on in the installation, so keep the volume IDs and the host name (Private DNS) of the EC2 instance ready.
The reason for this is that we will have to use Topology-Aware Volume Provisioning in Kubernetes.
For more information on Amazons EBS read Block Device Mapping.
The Kubernetes deployments will later on also be using nodeAffinity to successfully target the specific EC2 instance.
These are the services you will need to have set up in order to execute the deployment scripts correctly using Google Cloud Platform.
GKE is the Kubernetes cluster on Google Cloud Platform.
Setting up a GKE is quite easy using the Google cloud console.
Here is a nice guide on setting up a GKE using gcloud Creating a regional cluster.
We will need to set up a node group (node pool), Guide on node group setup.
For starters I would recommend creating a node pool with one VM backing it with 4 vCPU and 15 GB memory (n1-standard-4). Although by tweaking the deployment scripts minimum requirements for cpu you can deploy using a n1-standard-2 as well.
The GCR is the container registry, and it is required in order to host our custom built Docker images.
In order to create your first Google Container Registry, you should read the following page: Pushing and pulling images.
The way GCP handles persistent storage for Kubernetes clusters is by way of PD. We will have to provision some PD volumes for our components.
You can create the disks directly from Google cloud console.
Please make sure you create at least the following (10Gb is the minimum size for PD's):
- 10Gb PD volume for the Float component
- 10Gb PD volume for the Bridge component
- 10Gb PD volume for the Node
Please make sure you create the volumes in the same zone as the node pools VM, so the node can mount the volumes.
Also take note of the names of the PD's you create, since you will need to fill them into the values.yaml file in the helm sub folder.