> 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/open-agri-stack/deployment/separate-clusters.md).

# Separate Clusters

Departments on their own clusters.

Each namespace in the [reference topology](https://docs.openg2p.org/products/open-agri-stack/deployment.md#topology) is already installed as a separate organisation, so the same charts and choices work when each department, and the Exchange, run on their own clusters.

<figure><img src="https://3034178245-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZcdob2emEcLMvLyIxqT%2Fuploads%2Fgit-blob-15c71395b129a4b1bcdcf7aeb17842a9aeed47ef%2Fopen-agri-stack-separate-clusters.svg?alt=media" alt="Departments on separate clusters: the Agriculture Department&#x27;s cluster with the Farmer Registry (trial), the Crops Department&#x27;s cluster with the Crop Sown Registry (dept1), and the Exchange (agrix) in its own cluster or sharing one with a department. Each cluster has its own ingress and domain. The Composite calls each registry&#x27;s partner API by public hostname; each department&#x27;s Consent Manager reads the Exchange Consent Manager&#x27;s public keys from its public JWKS URL."><figcaption><p>Departments on separate clusters</p></figcaption></figure>

## What changes

| Step                                                                                          | On separate clusters                                                                                                                                                                                       |
| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Registries](https://docs.openg2p.org/products/open-agri-stack/deployment/farmer-registry.md) | Set **Exchange Domain** (Commons Services, Consent Manager group) to the Exchange's domain when it is not `agrix.<parent of this domain>`; or **Composite JWKS URL** when the Composite's hostname differs |
| [Exchange](https://docs.openg2p.org/products/open-agri-stack/deployment/exchange.md)          | The registries' search URLs are their public hostnames, as on one cluster                                                                                                                                  |
| [Testing](https://docs.openg2p.org/products/open-agri-stack/deployment/testing.md)            | Each credential in the test's configuration as an environment variable (`env`), since one `kubectl` context does not reach every cluster                                                                   |

Across clusters, these must be reachable with public DNS names and trusted TLS:

| From                                 | To                                                                                                                                   |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
| The Exchange (Composite)             | Each registry's partner API                                                                                                          |
| Each department (Consent Manager)    | The Exchange CM's public keys: `https://consent-manager-partner.<Exchange domain>/api/consent-manager-partner/.well-known/jwks.json` |
| Each department (Partner Management) | The Composite's public keys: `https://agri-composite.<Exchange domain>/.well-known/jwks.json`                                        |

Each department upgrades on its own schedule; after any upgrade, run the [test](https://docs.openg2p.org/products/open-agri-stack/deployment/testing.md) to check the whole path.

## Adding a department

1. Install its registry as on the [registry pages](https://docs.openg2p.org/products/open-agri-stack/deployment/farmer-registry.md), with **Exchange Role** `department`.
2. Add the registry to the Composite (`composite.registries` in **Edit YAML**) and to the use cases that read it ([adding a registry](https://docs.openg2p.org/products/open-agri-stack/registries/adding-a-registry.md)).
3. The department releases its registry's data: [Releasing Registry Data to the Composite](https://docs.openg2p.org/products/open-agri-stack/administration/releasing-data-to-the-composite.md).
4. Add the registry to the test's configuration (`registries`) and run the [test](https://docs.openg2p.org/products/open-agri-stack/deployment/testing.md).


---

# 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/open-agri-stack/deployment/separate-clusters.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.
