Backbone Deployment

On this page:

• Overview

• Pre-requisites

• Deployment steps

Overview

Once the cluster is ready and healthy you can start deploying backbones services.

Deploy configuration and deployment in the following Services Lists

1. Backbone (Redis, ZooKeeper-v2, Kafka-v2,elasticsearch-data-v1, elasticsearch-client-v1, elasticsearch-master-v1)

2. Gateway (Zuul, nginx-ingress-controller)

Pre-requisites

• Understanding of VM Instances, LoadBalancers, SecurityGroups/Firewalls, nginx, DB Instances, and data volumes.

• Experience with Kubernetes, Docker, Jenkins, helm, golang, Infra-as-code.

Deployment Steps

Deploy configuration and deployment backbone services:

1. Clone the git repo https://github.com/egovernments/eGov-infraOps . Copy existing dev.yaml and dev-secrets.yaml with new environment name (eg..yaml and-secrets.yaml)
2. Modify the global domain and set namespaces create to true

1. Modify the below-mentioned changes for each backbone service:

Eg. For Kafka-v2

1. If you are using AWS as a cloud provider, change the respective volume ids and zones. (You will get the volume ids and zone details from either a remote state bucket or from the AWS portal).

Eg. Kafka-v2

1. If you are using Azure cloud provider, change the diskName and diskUri. (You will get the volume ids and zone details from either the remote state bucket or from the Azure portal)

Eg. Kafka-v2

1. If you are using ISCSI , change the targetPortal and iqn.

1. Deploy the backbone services using the go command

cd /eGov-infraOps/egov-deployergo run main.go deploy -e dev -p -c 'kafka-v2,redis,zookeeper-v2,elasticsearch-data-v1,elasticsearch-master-v1,playground,cert-manager,kafka-connect,kafka-connect-restart-tasks,kibana-v1,nginx-ingress'

1. Modify the “dev” environment name with your respective environment name.

Flags:

• e --- Environment name

• p --- Print the manifest

• c --- Enable Cluster Configs

Check the status of pods

kubectl get pods --all-namespaces

​