> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/0.1.0-infra.md).

# 0.1.0 Infra

**Release Version:** v0.1.0 Infra

**Release Type:**

**Release Date:** 22nd January, 2026

### Overview

This release of the Rapid Deployment Model focuses on stability improvements, configuration fixes and expanded documentation to streamline deployments and reduce friction during setup and automation workflows.

### **Major Areas of Work**

* **Domain Configuration**
  * Removed domain hardcoding at the DevOps layer and the corresponding automation code is also fixed.
* **Documentation Improvements**
  * Added missing procedural documentation:
    * Captcha update steps.
    * GitHub Actions error logs.
    * Usage guides.
* **Bug Fixes**
  * Resolved minor issues including:
    * Naming inconsistencies.
    * Number sequencing problems.
* **Configuration Fixes**
  * Corrected config-server naming tag.
  * Resolved config mismatches.
  * Updated ClamAV image tag to correct version.

### Bug Fixes

<table><thead><tr><th width="192.21875">JIRA</th><th>Description</th></tr></thead><tbody><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44121">MOSIP-44121</a></td><td>Rapid Deployment –The documentation does not clearly explain how to configure Google reCAPTCHA.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44127">MOSIP-44127</a></td><td>Rapid Deployment-In step 3b, the cluster WireGuard values are taken from peer1.conf, but both values for the TF_WG_CONFIG secret and the CLUSTER_WIREGUARD_WG0 secret are using the same value.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44158">MOSIP-44158</a></td><td>Rapid Deployment – The rapid deployment documentation does not include details for Helmsman destroy workflows and observ-infra setup.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44117">MOSIP-44117</a></td><td>clamav pod was not coming up due to this not able to continue the rapid deployment.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44122">MOSIP-44122</a></td><td>Rapid Deployment – In the Terraform Apply section of the documentation, there is no information in the README on how to view Terraform run error logs.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-43518">MOSIP-43518</a></td><td>Stabilise the terraform-script for observ-infra.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-43519">MOSIP-43519</a></td><td>Missing 'v' prefix in Config-Server tag version in rapid deployment script.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-43521">MOSIP-43521</a></td><td>Elasticsearch fails to start on Ubuntu 24.04.3 AMI due to cgroup v2 incompatibility - NullPointerException in CgroupV2Subsystem.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-43525">MOSIP-43525</a></td><td>GlobalConfigMap domain hardcoded to .mosip.net</td></tr></tbody></table>

### Repository Released

| Repositories | Tags Released                                       |
| ------------ | --------------------------------------------------- |
| infra        | [0.1.0](https://github.com/mosip/infra/tree/v0.1.0) |

### Known Issues

| JIRA                                                          | Description                                                                                                                           |
| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| [MOSIP-43524](https://mosip.atlassian.net/browse/MOSIP-43524) | Rancher Monitoring CRD post-install script not modular in rapid deployment                                                            |
| [MOSIP-43522](https://mosip.atlassian.net/browse/MOSIP-43522) | Remove dry-run from Helmsman workflow of rapid deployment                                                                             |
| [MOSIP-43471](https://mosip.atlassian.net/browse/MOSIP-43471) | Resident API Test Rig- Skips observed failed due to esignet not deployed                                                              |
| [MOSIP-44290](https://mosip.atlassian.net/browse/MOSIP-44290) | Rapid: The domain name is hardcoded in DSL version 1.2.1.0, so we are currently using DSL version 1.3.0 for rapid deployment testing. |

### Documentation

* [Deployment Guide](https://docs.mosip.io/1.2.0/setup/deploymentnew/v3-installation/1.2.0.3)


---

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