K8s Cluster Requirement
- 1 Bastion- t2micro (Gateway) 2GB RAM 1vCore CPU
- 3 k8s Master- t2medium 4 GB RAM 2 vCore CPU
- 6 k8s Nodes with each 16GB RAM and 4 vCore CPUs
  OR
- AKS/EKS/GKE Managed Kubernetes Cluster Engine from AWS or Azure or GCP
- 6 k8s Nodes- m4large with each 16GB RAM and 4 vCore CPUs

Http Traffic/Routing:

Image Added Image Added

Kubernetes Cluster Provisioning

...

Choose your cloud provider (Azure, AWS, GCP or your private)
Choose to go with the cloud provider specific Kubernetes Managed Engine like AKS, EKS, GKE.
Follow the Cloud provider specific instruction to create a Kubernetes Cluster (stable version 1.11) with 5 to 6 worker nodes with 16GB RAM and 4 vCore CPU (m4.xlarge)
PostGres DB (Incase of AWS, Azure, GCP use the RDS) and have the DB server and the DB Credentials details.
Provision the disk volumes for Kafka, ES-Cluster and ZooKeeper as per the below baselines and gather the volume ID details.
Install Kubectl on DevOps local machine to interact with the cluster, setup kubeconfig with the allowed user credentials.

AKS on Azure

Image Added

Image Modified

2. Private Cloud - Manually setup Kubernetes Cluster:

Create a VPC or Virtual Private Network with multi availability zones
Provision the Linux VMs with any Container Optimised OS (CoreOS, RHEL, Ubuntu, Debian, etc) within the VPC Subnet.
Provision 1 Bastion Host that acts as proxy server to Kubernetes cluster Nodes.
3 Master Nodes with 4 GB RAM 2 vCore CPU
6 worker nodes with 16GB RAM and 4 vCore CPU
PostGres DB (Linux VM)
Provision the disk volumes for Kafka, ES-Cluster and ZooKeeper as per the below baselines and gather the volume ID details.
Create LoadBalancer or Ingress to talk to Kube API server that routes the external traffic to the services deployed on cluster.
Setup AuthN & AuthZ.
Install Kubectl on DevOps local machine to interact with the cluster, setup kubeconfig with the allowed user credentials

Image RemovedImage Modified Image Added

Deployment Architecture:

...

Python based Deployment script that reads the value from the Jinja 2 template and deploys into the cluster.
Each env will have one Jinja Template that will have the definition of services to be deployed, their dependancies like Config, Env, Secrets, DB Credentials, Persistent Volumes, Manifest, Routing Rules, etc..

Image Added

...

Image Removed

...

Image Added

Image AddedImage Added

Cluster/Service Monitoring

...

Versions Compared

Old Version 5

New Version 6

Key

Http Traffic/Routing:

Kubernetes Cluster Provisioning

Choose your cloud provider (Azure, AWS, GCP or your private)

Choose to go with the cloud provider specific Kubernetes Managed Engine like AKS, EKS, GKE.

Follow the Cloud provider specific instruction to create a Kubernetes Cluster (stable version 1.11) with 5 to 6 worker nodes with 16GB RAM and 4 vCore CPU (m4.xlarge)

PostGres DB (Incase of AWS, Azure, GCP use the RDS) and have the DB server and the DB Credentials details.

Provision the disk volumes for Kafka, ES-Cluster and ZooKeeper as per the below baselines and gather the volume ID details.

Install Kubectl on DevOps local machine to interact with the cluster, setup kubeconfig with the allowed user credentials.

AKS on Azure

Create a VPC or Virtual Private Network with multi availability zones

Provision the Linux VMs with any Container Optimised OS (CoreOS, RHEL, Ubuntu, Debian, etc) within the VPC Subnet.

Provision 1 Bastion Host that acts as proxy server to Kubernetes cluster Nodes.

3 Master Nodes with 4 GB RAM 2 vCore CPU

6 worker nodes with 16GB RAM and 4 vCore CPU

PostGres DB (Linux VM)

Provision the disk volumes for Kafka, ES-Cluster and ZooKeeper as per the below baselines and gather the volume ID details.

Install Kubectl on DevOps local machine to interact with the cluster, setup kubeconfig with the allowed user credentials

Deployment Architecture:

Python based Deployment script that reads the value from the Jinja 2 template and deploys into the cluster.

Each env will have one Jinja Template that will have the definition of services to be deployed, their dependancies like Config, Env, Secrets, DB Credentials, Persistent Volumes, Manifest, Routing Rules, etc..

Cluster/Service Monitoring

Page Comparison

Versions Compared

Old Version 5

New Version 6

Key

Http Traffic/Routing:

Kubernetes Cluster Provisioning

Choose your cloud provider (Azure, AWS, GCP or your private)

Choose to go with the cloud provider specific Kubernetes Managed Engine like AKS, EKS, GKE.

Follow the Cloud provider specific instruction to create a Kubernetes Cluster (stable version 1.11) with 5 to 6 worker nodes with 16GB RAM and 4 vCore CPU (m4.xlarge)

PostGres DB (Incase of AWS, Azure, GCP use the RDS) and have the DB server and the DB Credentials details.

Provision the disk volumes for Kafka, ES-Cluster and ZooKeeper as per the below baselines and gather the volume ID details.

Install Kubectl on DevOps local machine to interact with the cluster, setup kubeconfig with the allowed user credentials.

AKS on Azure

Create a VPC or Virtual Private Network with multi availability zones

Provision the Linux VMs with any Container Optimised OS (CoreOS, RHEL, Ubuntu, Debian, etc) within the VPC Subnet.

Provision 1 Bastion Host that acts as proxy server to Kubernetes cluster Nodes.

3 Master Nodes with 4 GB RAM 2 vCore CPU

6 worker nodes with 16GB RAM and 4 vCore CPU

PostGres DB (Linux VM)

Provision the disk volumes for Kafka, ES-Cluster and ZooKeeper as per the below baselines and gather the volume ID details.

Install Kubectl on DevOps local machine to interact with the cluster, setup kubeconfig with the allowed user credentials

Deployment Architecture:

Python based Deployment script that reads the value from the Jinja 2 template and deploys into the cluster.

Each env will have one Jinja Template that will have the definition of services to be deployed, their dependancies like Config, Env, Secrets, DB Credentials, Persistent Volumes, Manifest, Routing Rules, etc..

Cluster/Service Monitoring