> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/accelerators/concepts/deployment-key-concepts/backbone-deployment.md).
# Backbone Deployment
On this page:
* [Overview](#overview)
* [Pre-requisites](#pre-requisites)
* [Deployment steps](#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](https://github.com/egovernments/eGov-infraOps) . Copy existing [dev.yaml](https://github.com/egovernments/eGov-infraOps/blob/master/helm/environments/dev.yaml) and [dev-secrets.yaml](https://github.com/egovernments/eGov-infraOps/blob/master/helm/environments/dev-secrets.yaml) with new environment name (eg..yaml and-secrets.yaml)
2. Modify the global domain and set namespaces create to true
3. Modify the below-mentioned changes for each backbone service:
Eg. For Kafka-v2
4. 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
5. 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
6. If you are using **ISCSI ,** change the targetPortal and iqn.
7. 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'
```
8. 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
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.digit.org/platform/accelerators/concepts/deployment-key-concepts/backbone-deployment.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
