> 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/g2p-bridge/deployment/domain-names-and-certificates.md).

# Domain Names and Certificates

Domain names and mapping for G2P Bridge

## Domain names <a href="#domain-names" id="domain-names"></a>

The suggested convention is given below.

\<component>.\<environment>.\<your org domain>.\<tld>

The chart **derives every hostname from the install namespace** by default (`.Release.Namespace`), so you usually set nothing. Override `global.namespace` to use a hostname segment that differs from the Kubernetes namespace, or override each hostname individually.

| Component                  | Helm value                   | Example Domain (namespace = `trial`)       |
| -------------------------- | ---------------------------- | ------------------------------------------ |
| G2P Bridge Partner API     | `global.g2pBridgeHostname`   | `g2p-bridge.trial.openg2p.org`             |
| Beneficiary Portal API     | `global.benePortalHostname`  | `g2p-bridge-bene-portal.trial.openg2p.org` |
| Example Bank API (bundled) | `global.exampleBankHostname` | `example-bank.trial.openg2p.org`           |

All the above domains point to the Nginx IP for the server (virtual host) that routes to the Istio Ingress gateway on the [OpenG2P Cluster](https://docs.openg2p.org/deployment/base-infrastructure/openg2p-cluster).

## Certificates

SSL certs for all the above must be available, generally as a wild card certificate for the domain, example. `*.dev.openg2p.org`<br>


---

# 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/g2p-bridge/deployment/domain-names-and-certificates.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.