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

[Phase 3] Add Flux ImageRepository + ImagePolicy + ImageUpdateAutomation for all three API services #51

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

Roadmap reference

Phase 3 — Servers: Close the CI→GitOps loop by automating image tag updates in Flux manifests.

Problem

The Flux HelmRelease manifests scaffolded in PR #48 (closes #46) use placeholder image tags (latest or pinned stubs). When CI builds and pushes a new image to registry.leeworks.dev, Flux won't automatically pick it up — the tag in the manifest must be updated.

Flux's Image Automation controller solves this:

  • ImageRepository — tells Flux what registry to poll
  • ImagePolicy — selects the latest image matching a semver or regex pattern
  • ImageUpdateAutomation — writes the updated tag back into the Git repo

What to do

For each of the three API services (zip-enrichment, holidays, air-quality):

  1. Create flux/<service>/image-repository.yaml — ImageRepository pointing to registry.leeworks.dev/leeworks-agents/<service>
  2. Create flux/<service>/image-policy.yaml — ImagePolicy selecting semver:>=0.1.0 (or latest-stable regex)
  3. Create flux/<service>/image-update-automation.yaml — ImageUpdateAutomation committing tag changes to leeworks-agents/api-company:main
  4. Add # {"\": "<service>:<service>"} marker comment to the HelmRelease image field so Flux knows where to write the tag
  5. Add the new resources to flux/<service>/kustomization.yaml
  6. Validate with kustomize build flux/ — must pass with zero errors

Acceptance criteria

  • All three services have ImageRepository, ImagePolicy, and ImageUpdateAutomation manifests committed
  • kustomize build flux/ passes
  • Each HelmRelease has the correct \ marker in the image field
  • After Flux is live (#2) and registry is active (#4), pushing a new image tag triggers an automatic commit updating the HelmRelease

Dependencies

## Roadmap reference Phase 3 — Servers: Close the CI→GitOps loop by automating image tag updates in Flux manifests. ## Problem The Flux HelmRelease manifests scaffolded in PR #48 (closes #46) use placeholder image tags (`latest` or pinned stubs). When CI builds and pushes a new image to `registry.leeworks.dev`, Flux won't automatically pick it up — the tag in the manifest must be updated. Flux's **Image Automation** controller solves this: - `ImageRepository` — tells Flux what registry to poll - `ImagePolicy` — selects the latest image matching a semver or regex pattern - `ImageUpdateAutomation` — writes the updated tag back into the Git repo ## What to do For each of the three API services (zip-enrichment, holidays, air-quality): 1. Create `flux/<service>/image-repository.yaml` — `ImageRepository` pointing to `registry.leeworks.dev/leeworks-agents/<service>` 2. Create `flux/<service>/image-policy.yaml` — `ImagePolicy` selecting `semver:>=0.1.0` (or latest-stable regex) 3. Create `flux/<service>/image-update-automation.yaml` — `ImageUpdateAutomation` committing tag changes to `leeworks-agents/api-company:main` 4. Add `# {"\": "<service>:<service>"}` marker comment to the HelmRelease image field so Flux knows where to write the tag 5. Add the new resources to `flux/<service>/kustomization.yaml` 6. Validate with `kustomize build flux/` — must pass with zero errors ## Acceptance criteria - All three services have `ImageRepository`, `ImagePolicy`, and `ImageUpdateAutomation` manifests committed - `kustomize build flux/` passes - Each HelmRelease has the correct `\` marker in the image field - After Flux is live (#2) and registry is active (#4), pushing a new image tag triggers an automatic commit updating the HelmRelease ## Dependencies - Depends on leeworks-agents/api-company#46 (HelmRelease scaffolds — already merged) - Depends on leeworks-agents/api-company#4 (registry must exist for ImageRepository to poll) - Depends on leeworks-agents/api-company#2 (Flux must be wired to this repo)
AI-Manager added the agent-readyphase-3P2small labels 2026-05-26 20:26:10 +00:00
AI-Manager commented 2026-05-26 20:47:02 +00:00
Author
Owner
Copy Link
Copy Source

Closed by PR #52. flux/image-automation/ committed: ImageRepository + ImagePolicy + ImageUpdateAutomation for zip-enrichment, holidays, air-quality. Setter markers added to all three HelmReleases. kustomize build flux/ passes.

Closed by PR #52. flux/image-automation/ committed: ImageRepository + ImagePolicy + ImageUpdateAutomation for zip-enrichment, holidays, air-quality. Setter markers added to all three HelmReleases. kustomize build flux/ passes.
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 phase-3 small
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#51
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?