> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/registry/registry/_archive/social-registry/deployment/helm-packaging-guide.md).

# Registry Helm Chart 2.x

How to create a Helm Package for Social Registry

{% hint style="warning" %}
The material here applies to all Social Registry charts with 2.x versions. The environment deployment architecture going forward is changed and consequently the charts have changed too. For newer charts refer to documentation on 3.x version of charts and above
{% endhint %}

## Creation of Helm Chart

Below are steps to create 2.x Helm Chart for Registry ().

### Tagging Helm repo

The charts are located in [this](https://github.com/OpenG2P/openg2p-social-registry-deployment/) repo.

1. Decide on which branch you would like to create the tag.
2. On the marked branch, create another temporary branch with the same name as the version, e.g. 1.3.1 (or some generic name like `temp`).
3. On this branch make the necessary changes in the chart:
   1. Update all `Chart.yaml` files. Make sure 3 digit version without any suffix is updated in the file.
   2. Update any dependency chart versions. Make sure all the versions of other charts are frozen versions (not develop/prerelease versions).
   3. Update `values.yaml` with the tagged version of all the Docker images. (There are multiple places where tags of docker images have to be updated. Find all lines containing `image:`.)
4. Commit the changes on this branch
5. Create a tag following tagging conventions out of this temporary branch. E.g. `v1.3.1`.
6. The GitHub workflow action to package Helm charts and push to the `openg2p-helm` repo should be triggered automatically.
7. Delete the temporary branch that was created in the above steps.
8. Update the [Versions](/products/registry/registry/_archive/social-registry/versions.md) page on this documentation.
9. Once the GitHub actions are finished, the packages should be available on Rancher also (Use the refresh button on the Rancher Charts page to see the latest versions).

{% hint style="warning" %}
Do NOT make these changes to the temporary branch directly on GitHub. Create the temporary branch on GitHub first, commit all the changes locally, and then make a push to the temporary branch from local. (This is done this way because of how the GitHub action gets triggered.)
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openg2p.org/products/registry/registry/_archive/social-registry/deployment/helm-packaging-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.