Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »



Cluster Sizing:

  • Base Minimal Services:
    • 50+ Services
      • Core, Dashboard, PGR, PT, TL, Billing, Reports, HRMS, etc.
      • Telemetry, Infra, Kafka, ES, ZooKeeper, Zuul, nginx, etc.
    • 100+ Pods (egov, monitoring, logging, es-cluster, Kafka, backbone)


  • K8s Cluster Requirement
    • 1 Bastion- t2micro (Gateway) 2GB RAM 1vCore CPU
    • 2 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

Kubernetes Cluster Provisioning 

  1. Managed Kubernetes Engine:

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

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

  3. 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)

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

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

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

      

      2. Private Cloud - Manually setup Kubernetes Cluster:

  1. Create a VPC or Virtual Private Network with multi availability zones 

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

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

  4. 2 Master Nodes with 4 GB RAM 2 vCore CPU

  5. 6 worker nodes with 16GB RAM and 4 vCore CPU

  6. PostGres DB (Linux VM)

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

  8. Create LoadBalancer or Ingress to talk to Kube API server that routes the external traffic to the services deployed on cluster.
  9. Setup AuthN & AuthZ. 

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





Deployment Architecture:

  • Every code commit is well reviewed and merged to master branch through Pull Requests

  • Each merge triggers a new CI Pipeline that ensures CodeQuality and CITests before building the artefacts.

  • Artefact are version controlled and pushed to Artifactory like Nexus.

  • After successful CI Jenkins bakes the Docker Images with the Latest Artefacts and pushed the newly baked docker image to Docker Repo.

  • Deployment Pipeline pulls the Image and pushes to the corresponding Env.

       Deployment Scripts:

  • 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 


  • Monitoring


    1. Prometheus / CloudWatch for node monitoring
    2. Prometheus for pod level monitoring


  • Logging


    1. Logs are tagged with correlation-id
    2. Fluent-bit for log scraping
    3. Kafka for temporary log storage and processing
    4. Kafka connect to push logs to various sinks
    5. Elasticsearch [sink] / Kibana for visualizations


  • Tracing


    1. Jaeger for distributed tracing
    2. Traces are tagged with correlation-id






Mutistate Cluster Orchestration and Management



              


  • No labels