> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-5/4-create-the-workload-spokes.md).

# 4. Create the workload Spokes

The application environments are named `information-mediator` and `example-workloads`. We create both with the same configuration, rendering and Git delivery sequence, using `role: spoke` for their workload role. Each has its own machine counts, API endpoint, credential references and application-delivery permissions. [\[9\]](https://git.vanillacore.net/govstack/govstack-bootstrap/src/commit/1195f539afe5a1018be07d2e1865824c225ee407/docs/spoke-lifecycle.md)[\[13\]](https://git.vanillacore.net/govstack/govstack-bootstrap/src/commit/1195f539afe5a1018be07d2e1865824c225ee407/templates/loadbalancer-foundation-apps.yaml.j2)

We choose separate environments when access requirements, release schedules or the consequences of a failure justify independent operation. A Spoke can serve one application or a business domain whose applications share those requirements. We also account for shared dependencies: the reference deployment uses a common private OpenStack network, so its network rules remain part of the separation design. [\[9\]](https://git.vanillacore.net/govstack/govstack-bootstrap/src/commit/1195f539afe5a1018be07d2e1865824c225ee407/docs/spoke-lifecycle.md)

Their addresses, Pod and Service ranges and VPN settings come from the plan in Step 4. Image IDs and infrastructure IDs come from the outputs recorded during the Management installation.

For each workload Spoke, we follow provisioning and foundation delivery until its current observations show the requested machines ready and its foundation Applications healthy. We then record its private Envoy Service address. Those addresses connect the LoadBalancer Spoke to the two destinations. The [workload-Spoke walkthrough](https://git.vanillacore.net/giga/content/src/branch/main/chapter-5/lab/walkthroughs/04-two-spokes.md) supplies the full creation and observation sequence.

## Prepare application delivery

The local Argo CD needs an application repository and destination namespace. We configure them through a **tenant**, an application-delivery scope that permits the chosen repositories and namespaces. Platform services and environment lifecycle continue to be managed centrally. [\[3\]](https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md)[\[13\]](https://git.vanillacore.net/govstack/govstack-bootstrap/src/commit/1195f539afe5a1018be07d2e1865824c225ee407/templates/loadbalancer-foundation-apps.yaml.j2)

The HTTP service used below runs in namespace `chapter5-probe`. Its repository supplies a Deployment, Service, Certificate and HTTPProxy. Local Argo CD delivers those resources into that namespace. Before the first release, we confirm repository access, namespace permissions and a certificate issuer in the destination Spoke.


---

# 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://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-5/4-create-the-workload-spokes.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.