# 0.2.0 Infra

**Release Version**: 0.2.0 Infra

**Release Type**: Minor Release

**Release Date**: 24th March, 2026

### Overview

The current release of **0.2.0 Infra** (**Rapid Deployment Infra**) introduces integration with [**eSignet 1.4.2**](https://docs.esignet.io/roadmap-and-releases/versions/v1.6.2), enabling a flawless deployment of MOSIP platform along with now a seamless deployment of eSignet-dependent features, which earlier were getting skipped.

It also resolves key infrastructure issues impacting RKE2 cluster installations and addresses multiple bugs across CI/CD workflows, alerting mechanisms, and deployment scripts.

Overall, the release improves deployment reliability, automation stability, and environment configuration handling.

### **Major Highlights/Features**

* **eSignet 1.4.2 Integration** With the current release 0.2.0 Infra, eSignet 1.4.2 is fully integrated/configured into the Helmsman deployment framework, enabling end-to-end deployment of all eSignet-dependent features. In earlier releases, flows requiring eSignet-based authentication, such as OTP verification, biometric authentication, KYC exchange, and Resident Portal/Service interactions were getting skipped during deployment. These flows are now executed as part of the standard deployment pipeline.
* **Improved Deployment Reliability** Resolved issues in Helm deployment scripts to ensure resources are correctly applied to the cluster rather than just rendered locally.
* **Stabilized CI/CD Workflows** Fixed critical issues in GitHub Actions workflows for Helmsman and Terraform, ensuring smooth and reliable automated deployments.
* **Enhanced Monitoring & Alerting** Corrected alerting hooks configuration to ensure proper triggering of notifications across monitoring systems.

### **Upgrade Notes**

* Review and update any Ansible playbooks using deprecated configurations before upgrading cluster nodes.
* Ensure rancher\_import\_url is correctly configured or left empty if Rancher import is disabled.
* Re-run GitHub Actions workflows post-upgrade to leverage fixed CI/CD pipelines.
* Verify that deployment scripts use helm install instead of helm template for proper cluster deployments.

### Story Released

<table><thead><tr><th width="202.42578125">JIRA</th><th>Description</th></tr></thead><tbody><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-43143">MOSIP-43143</a></td><td>eSignet 1.4.2 integration with Helmsman.</td></tr></tbody></table>

#### Bug Fixes

<table><thead><tr><th width="202.07421875">JIRA</th><th>Description</th></tr></thead><tbody><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44253">MOSIP-44253</a></td><td>Ansible deprecated configurations causing RKE2 installation failures; rancher_import_url validation fix.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44479">MOSIP-44479</a></td><td>Fix helm install command instead of helm template in install.sh</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44483">MOSIP-44483</a></td><td>Fix GitHub Actions workflow bugs in helmsman and terraform workflows.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44481">MOSIP-44481</a></td><td>Alerting hooks script is incorrect.</td></tr></tbody></table>

#### Repositories Released

<table><thead><tr><th width="205.140625">Repository</th><th>Tags</th></tr></thead><tbody><tr><td><strong>infra</strong></td><td><a href="https://github.com/mosip/infra/tree/v0.2.0"><strong>0.2.0</strong></a></td></tr><tr><td><strong>mosip-config</strong></td><td><a href="https://github.com/mosip/mosip-config/tree/v1.2.4.3-beta2"><strong>v1.2.4.3-beta2</strong></a></td></tr><tr><td><strong>mosip-helm</strong></td><td><a href="https://github.com/mosip/mosip-helm/tree/v1.2.0.4"><strong>v1.2.0.4</strong></a></td></tr><tr><td><strong>k8s-infra</strong></td><td><a href="https://github.com/mosip/k8s-infra/tree/v1.2.1.2"><strong>v1.2.1.2</strong></a></td></tr></tbody></table>

#### Known Issues

<table><thead><tr><th width="204.53125">JIRA</th><th>Description</th></tr></thead><tbody><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44566">MOSIP-44566</a></td><td>Rapid Deployment - API TestRig resident deployment fails due to machine not automatically activating in admin portal.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-43522">MOSIP-43522</a></td><td>Remove dry-run from Helmsman workflow of rapid deployment.</td></tr></tbody></table>

#### Documentation

* [MOSIP Rapid Deployment Infrastructure](https://github.com/mosip/infra/blob/v0.2.0/README.md)
* [Deployment Guide](https://docs.mosip.io/1.2.0/setup/deploymentnew/v3-installation/1.2.0.3)
* [eSignet Deployment](https://github.com/mosip/infra/blob/master/docs/esignet_README.md)
* [Test Report](https://github.com/mosip/test-management/tree/master/Platform%20release/Rapid%20Deployment%20Testing-0.2.0)


---

# 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.mosip.io/1.2.0/roadmap-and-releases/releases/0.2.0-infra.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.