# Deployment

The Registry is deployed over Kubernetes infrastructure that offers **production-grade** deployment along with powerful security, access control and operational features. Learn more about the deployment architecture [here](/operations/deployment/concepts.md).

## Deployment steps

1. [Infrastructure deployment](/operations/deployment/deployment-instructions/infrastructure-setup.md)
2. [Environment creation](/operations/deployment/deployment-instructions/environment-installation.md)
3. Registry installation

## Registry installation

After the steps 1 and 2, since Rancher will be up and running it is recommend that deployment of Registry is done from Rancher UI.

### Prerequisites

1. Infastructure and environment is created as given above
2. You have full admin rights to the cluster and Rancher UI.

### Installation

1. Login to Rancher console
2. Select the cluster and namespace (environment)
3. Under Apps -> Repositories make sure the repository <https://openg2p.github.io/openg2p-helm/rancher> is added
4. Under Apps->Charts refresh all repositories
5. Select "OpenG2P Registry" chart
6. Select the version (*3 digit versions denote frozen versions, while version with -develop tag are moving versions*).
7. On Install Step1
   1. select namespace
   2. give a name to the installation - 'registry' recommended
   3. select 'Customize Helm options before install'
   4. Next
8. Review all variables. Typically you will not need to change anything except for **ID Generator** where your ID types may be differen&#x74;**.**
9. Install
10. Wait for all pods to come up successfully

### Post install check

1. On browser open site 'registry.\<you domain>'.
2. This should open the Keycloak login page. Give 'admin' as user name and 'admin' as password
3. You will be prompted to change the password. Change to a strong password.
4. You should see the Registry home/landing/dashboard page.


---

# Agent Instructions: 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:

```
GET https://docs.openg2p.org/products/registry/registry/deployment.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.