# Component -> Workflow Mapping

This file maps O11Y components to their CD workflow, trigger inputs, and
namespace scope.

Use the namespace scope here for both:

- Prometheus verification queries in `references/monitoring.md`
- Emergency rollback commands in `SKILL.md`

Do **not** assume every component lives only in `observability`.

> Region/group metadata source:
> [`deployments/deploy-groups.txt`](../../../deployments/deploy-groups.txt)

## Regional Server

- Workflow: `.github/workflows/regional-server-cd.yaml`
- Name: `Regional Server CD`
- Inputs: `git-ref`, `env`, `region`, `vendor`,
  `regional-server-image` (optional), `data-server-image` (optional), `aws-role-arn` (optional)
- Namespaces: `observability`

## Global Server

- Workflow: `.github/workflows/global-server-cd.yaml`
- Name: `Global Server CD`
- Inputs: `git-ref`, `env`
- Namespaces: `kong`, `observability`
- Notes: `kong` is deployed in `kong`; `karma` and `promxy` are deployed in
  `observability`.

## DrHouse

- Workflow: `.github/workflows/drhouse-cd.yaml`
- Name: `DrHouse CD`
- Inputs: `git-ref`, `env`, `region`, `vendor`, `aws-role-arn` (optional)
- Namespaces: `observability`, `observability-client`
- Notes: most DrHouse components deploy to `observability`; `auth-server`
  deploys to `observability-client` only for the prod AWS `us-west-2` path.

## Dataplane

- Workflow: `.github/workflows/dataplane-cd.yaml`
- Name: `Dataplane CD`
- Inputs: `git-ref`, `env`, `region`, `vendor`, `aws-role-arn` (optional), `ops-server-url` (optional)
- Namespaces: `observability`, `default`
- Notes: `vmcluster` and `loki-ha` deploy in `observability`;
  `alertmanager-regional` deploys in `default`.

## Cloud Addon

- Workflow: `.github/workflows/cloud-addon-cd.yaml`
- Name: `Cloud Addon CD`
- Inputs: `git-ref`, `env`, `region`, `vendor`, `aws-role-arn` (optional)
- Namespaces: `kube-system`, `observability`
- Notes: most cloud-addon components deploy in `kube-system`; the
  `ingress-nginx-read` release uses `observability` on Azure.

## Infra

- Workflow: `.github/workflows/infra-cd-v2.yaml`
- Name: `Infra`
- Inputs: `git-ref`, `group-list` (optional)
- Namespaces: `self-monitoring`, `kube-system`, `observability`,
  `cluster-backup`, `ops-system`
- Notes: infra spans multiple namespaces. Examples include
  `kube-prometheus-stack`, `o11y-mixin`, `victoria-metrics-operator`,
  `volume-autoscaler`, and `vector` in `self-monitoring`; `cert-manager` and
  `eventrouter` in `kube-system`; `external-secret` resources in
  `observability`; `velero` in `cluster-backup`; and managed `ops-server` in
  `ops-system`.