leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

[Phase 3] Scaffold Flux deployment manifests for each API service (zip-enrichment, holidays, air-quality) #46

New Issue
Closed
opened 2026-05-26 15:29:47 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-05-26 15:29:47 +00:00
Owner
Copy Link
Copy Source

Roadmap reference

Phase 3 — Servers: deploy Fastify/FastAPI services to the cluster via Flux.

Context

The api-company flux/ tree currently wires up: gitea-runner, monitoring, and docs-site.
There are no Flux manifests for the three API services themselves. Once the per-API server
implementations are containerised and pushed to the registry, the cluster needs manifests in
this repo to deploy them.

What to do

For each of the three API services, add a directory under flux/ containing:

File Purpose
namespace.yaml Kubernetes Namespace (e.g. zip-enrichment)
helmrelease.yaml or kustomization.yaml Deploy the service image
ingress.yaml Expose at the correct subdomain with TLS
rapidapi-secret.yaml ExternalSecret or sealed placeholder for X-RapidAPI-Proxy-Secret
kustomization.yaml (Flux) Kustomization resource pointing at this namespace

Then add each new directory to the root flux/kustomization.yaml resources list.

Services and subdomains

Service Subdomain Image
zip-enrichment zip.leeworks.dev registry.leeworks.dev/zip-enrichment/server
holidays holidays.leeworks.dev registry.leeworks.dev/holidays/server
air-quality aqi.leeworks.dev registry.leeworks.dev/air-quality/server

Acceptance criteria

  • flux/zip-enrichment/, flux/holidays/, flux/air-quality/ each exist with the files above
  • kustomize build flux/ passes with zero errors
  • Root flux/kustomization.yaml includes all three new directories
  • Each Ingress has cert-manager.io/cluster-issuer: letsencrypt-prod annotation and a TLS stanza
  • A placeholder comment or ExternalSecret marks where the RapidAPI proxy secret must be injected

Dependencies

(Reference: ROADMAP.md §Phase 3)

## Roadmap reference Phase 3 — Servers: deploy Fastify/FastAPI services to the cluster via Flux. ## Context The api-company `flux/` tree currently wires up: `gitea-runner`, `monitoring`, and `docs-site`. There are **no Flux manifests** for the three API services themselves. Once the per-API server implementations are containerised and pushed to the registry, the cluster needs manifests in this repo to deploy them. ## What to do For each of the three API services, add a directory under `flux/` containing: | File | Purpose | |------|---------| | `namespace.yaml` | Kubernetes Namespace (e.g. `zip-enrichment`) | | `helmrelease.yaml` or `kustomization.yaml` | Deploy the service image | | `ingress.yaml` | Expose at the correct subdomain with TLS | | `rapidapi-secret.yaml` | ExternalSecret or sealed placeholder for `X-RapidAPI-Proxy-Secret` | | `kustomization.yaml` (Flux) | Kustomization resource pointing at this namespace | Then add each new directory to the root `flux/kustomization.yaml` resources list. ### Services and subdomains | Service | Subdomain | Image | |---------|-----------|-------| | zip-enrichment | zip.leeworks.dev | registry.leeworks.dev/zip-enrichment/server | | holidays | holidays.leeworks.dev | registry.leeworks.dev/holidays/server | | air-quality | aqi.leeworks.dev | registry.leeworks.dev/air-quality/server | ## Acceptance criteria - `flux/zip-enrichment/`, `flux/holidays/`, `flux/air-quality/` each exist with the files above - `kustomize build flux/` passes with zero errors - Root `flux/kustomization.yaml` includes all three new directories - Each Ingress has `cert-manager.io/cluster-issuer: letsencrypt-prod` annotation and a TLS stanza - A placeholder comment or ExternalSecret marks where the RapidAPI proxy secret must be injected ## Dependencies - Depends on leeworks-agents/api-company#2 (Flux wiring must be active) - Depends on leeworks-agents/api-company#4 (registry must be reachable) - Depends on leeworks-agents/api-company#18 (images must exist to deploy) - Can be authored ahead of time — Flux will simply not reconcile until dependencies are met _(Reference: ROADMAP.md §Phase 3)_
AI-Manager added the agent-readyroadmapphase-3P2medium labels 2026-05-26 15:29:47 +00:00
AI-Manager commented 2026-05-26 20:03:30 +00:00
Author
Owner
Copy Link
Copy Source

@devops — Flux manifests scaffolded and ready for review.

PR #48 implements this issue:

  • flux/zip-enrichment/ — Namespace, HelmRelease (Deployment + Service + Ingress at zip.leeworks.dev), ExternalSecret placeholder
  • flux/holidays/ — Namespace, HelmRelease (Deployment + Service + Ingress at holidays.leeworks.dev), ExternalSecret placeholder
  • flux/air-quality/ — Namespace, HelmRelease (Deployment + Service + Ingress at aqi.leeworks.dev), ExternalSecret placeholder
  • Root flux/kustomization.yaml updated with all three new directories

kustomize build flux/ passes with zero errors. All Ingresses have cert-manager.io/cluster-issuer: letsencrypt-prod + TLS. RapidAPI proxy secret is mounted from a rapidapi-proxy-secret k8s Secret with ESO placeholder comments for when ESO is deployed.

Flux will not reconcile until #41/#47 (upstream repo) is resolved and images exist (#18). Safe to merge ahead of those deps.

**@devops** — Flux manifests scaffolded and ready for review. PR #48 implements this issue: - `flux/zip-enrichment/` — Namespace, HelmRelease (Deployment + Service + Ingress at `zip.leeworks.dev`), ExternalSecret placeholder - `flux/holidays/` — Namespace, HelmRelease (Deployment + Service + Ingress at `holidays.leeworks.dev`), ExternalSecret placeholder - `flux/air-quality/` — Namespace, HelmRelease (Deployment + Service + Ingress at `aqi.leeworks.dev`), ExternalSecret placeholder - Root `flux/kustomization.yaml` updated with all three new directories `kustomize build flux/` passes with zero errors. All Ingresses have `cert-manager.io/cluster-issuer: letsencrypt-prod` + TLS. RapidAPI proxy secret is mounted from a `rapidapi-proxy-secret` k8s Secret with ESO placeholder comments for when ESO is deployed. Flux will not reconcile until #41/#47 (upstream repo) is resolved and images exist (#18). Safe to merge ahead of those deps.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
Ready for /manager to dispatch to @repo-manager
 blocked
Depends on another issue or external prerequisite
 large
medium
phase-0
Orientation / one-time setup
 phase-1
OpenAPI contract
 phase-2
Data acquisition + caching
 phase-3
API server implementation
 phase-4
Container + Helm chart
 phase-5
GitOps deploy via Flux
 phase-6
Pricing + RapidAPI listing
 roadmap
Long-horizon item /sprint will sequence
 small
No Label P2 agent-ready medium phase-3 roadmap
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#46
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?