Route api-gateway to control-plane monolith#40
Conversation
Replace four manager services in compose and helm with one control-plane image. Keep Traefik on :9080; update routes, postgres init, and docs. Assisted-By: Claude (Anthropic) Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
gciavarrini
requested review from
gabriel-farache,
jenniferubah,
machacekondra and
ygalblum
as code owners
gciavarrini
changed the title
|
I think since we don't use micro-service architecture, there is no need for api-gateway now. Or why do you think we need it? |
@jenniferubah and I had the same doubt. But do we have a way to easily deploy the full dcm stack? Like UI + control plane + managers? |
I would keep everything in |
But we agreed to have managers (sp, placement, policy, catalog) in control-plane, while all the SPs (e.g. |
Closing in favor of consolidating deploy into control-plane (compose + helm, no Traefik). With the monolith, api-gateway no longer adds routing value. I'll follow up with a PR there. |
Move full-stack Compose and Helm packaging from api-gateway Details: - Compose: dcm-ui, optional SP profiles, API on `:8080` (no Traefik) - Helm chart migrated without gateway; routes hit control-plane directly - `compose-down` disconnects Kind and cleans up legacy `deploy_default` - Runbook and Kind setup docs under `deploy/` Supersedes: dcm-project/api-gateway#40 Fixes: [FLPATH-4239](https://redhat.atlassian.net/browse/FLPATH-4239) --- Assisted-By: Claude (Anthropic) Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
2 participants
Switch the api-gateway stack from four manager services to the control-plane monolith once PR #9 publishes
quay.io/dcm-project/control-plane.Replace manager containers in Compose and Helm with a single control-plane service.
Keep Traefik on
:9080and route catalog, policy, and SP APIs to the monolith.Point service provider registration at control-plane.
Create one
control-planePostgres database.