Deployment Documentation Index¶
Start here¶
This guide explains how partner applications get built, published, and deployed on the platform.
To keep the instructions reusable for any partner, we use placeholder names like ENTITY_NAMESPACE instead of one specific value. Wherever you see a placeholder, replace it with your own — for example, ENTITY_NAMESPACE becomes france-titres.
Everything described here is based on two real repositories, so you can always click through and check the actual configuration:
- hello-world-main/ — the application source code
- helm-hello-world-main/ — the Helm chart used to deploy it
Platform tools¶
| Tool | Link |
|---|---|
| GitLab | Link |
| Harbor | Link |
| Argo CD | Link |
Placeholder names used in this guide¶
Read 00-overview.md first — it explains these names and how they fit together:
| Placeholder | What it means |
|---|---|
ENTITY_NAMESPACE |
Your entity/partner name (example: france-titres) |
APP_SLUG |
Your application's identifier |
REGISTRY_HOST |
The container registry's hostname |
K8S_NAMESPACE |
The Kubernetes namespace your app runs in |
RELEASE_NAME |
The name given to your Helm release |
Reading order¶
| File | What you'll learn |
|---|---|
00-overview.md |
The big picture and the placeholder names |
01-build-and-image-publish.md |
How the Docker image is built, tagged, and published |
02-gitlab-cicd-pipeline.md |
What the GitLab pipeline actually does |
03-helm-chart-deployment.md |
How the Helm chart deploys your app |
04-virtualservice-routing.md |
How traffic is routed to your app |
05-argocd-application.md |
How Argo CD keeps your app in sync |
About the sources¶
Every page links to the real files it describes, so if something looks outdated you can check the source directly. Where something isn't confirmed by the code, it's called out as an assumption instead of stated as fact.