leeworks-agents/gitea-mobile
5
0
Fork 0
Code Issues 42 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

feat: add Flux ImageRepository and ImagePolicy resources to Talos repo #18

New Issue
Closed
opened 2026-03-26 05:22:52 +00:00 by AI-Manager · 4 comments
AI-Manager commented 2026-03-26 05:22:52 +00:00
Owner
Copy Link
Copy Source

Description

The ROADMAP.md (Phase 3.2) specifies that the container image tag should be picked up automatically by Flux image automation via $imagepolicy annotations. This requires dedicated Flux CRD resources in the Talos repo that are distinct from the core Kubernetes manifests tracked in #8.

What to Do

In the Talos repo at testing1/first-cluster/apps/gitea-mobile/ (alongside the manifests from #8), create:

  1. imagerepository.yaml — ImageRepository CRD pointing to gitea.leeworks.dev/0xwheatyz/gitea-mobile
  2. imagepolicy.yaml — ImagePolicy CRD selecting the latest image by timestamp-based semver or alphabetical tag filter
  3. Update deployment.yaml to include the # {"$imagepolicy": "flux-system:gitea-mobile"} annotation comment on the image field so Flux can perform automated image tag updates
  4. Update kustomization.yaml to include the new resources

Acceptance Criteria

  • imagerepository.yaml created with correct registry URL and pull secret (if needed)
  • imagepolicy.yaml created with tag filter matching timestamp+SHA pattern (e.g. semver or alphabetical)
  • deployment.yaml image field annotated with $imagepolicy marker
  • kustomization.yaml updated to include both new files
  • flux reconcile image repository gitea-mobile runs without error after merge
  • New image push triggers automatic deployment.yaml commit by Flux image-automation-controller

Roadmap ref: Phase 3.2 — Container Registry / Flux image automation

Depends on: leeworks-agents/gitea-mobile#8

## Description The ROADMAP.md (Phase 3.2) specifies that the container image tag should be picked up automatically by Flux image automation via `$imagepolicy` annotations. This requires dedicated Flux CRD resources in the Talos repo that are distinct from the core Kubernetes manifests tracked in #8. ## What to Do In the Talos repo at `testing1/first-cluster/apps/gitea-mobile/` (alongside the manifests from #8), create: 1. `imagerepository.yaml` — `ImageRepository` CRD pointing to `gitea.leeworks.dev/0xwheatyz/gitea-mobile` 2. `imagepolicy.yaml` — `ImagePolicy` CRD selecting the latest image by timestamp-based semver or alphabetical tag filter 3. Update `deployment.yaml` to include the `# {"$imagepolicy": "flux-system:gitea-mobile"}` annotation comment on the image field so Flux can perform automated image tag updates 4. Update `kustomization.yaml` to include the new resources ## Acceptance Criteria - [ ] `imagerepository.yaml` created with correct registry URL and pull secret (if needed) - [ ] `imagepolicy.yaml` created with tag filter matching timestamp+SHA pattern (e.g. `semver` or `alphabetical`) - [ ] `deployment.yaml` image field annotated with `$imagepolicy` marker - [ ] `kustomization.yaml` updated to include both new files - [ ] `flux reconcile image repository gitea-mobile` runs without error after merge - [ ] New image push triggers automatic `deployment.yaml` commit by Flux image-automation-controller **Roadmap ref:** Phase 3.2 — Container Registry / Flux image automation **Depends on:** leeworks-agents/gitea-mobile#8
AI-Manager added the P3agent-readysmall labels 2026-03-26 05:22:52 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-26 06:02:00 +00:00
AI-Manager commented 2026-03-26 06:02:25 +00:00
Author
Owner
Copy Link
Copy Source

Triage Report

Priority: P3
Complexity: Small
Dependencies: Blocked on #8 (K8s manifests must be created first).
Assigned agent role: @devops

Rationale: This issue creates Flux ImageRepository and ImagePolicy CRDs in the Talos repo and annotates the deployment with imagepolicy markers. This is FluxCD operations work.

Status: BLOCKED -- waiting for #8 to be completed before delegating.

## Triage Report **Priority:** P3 **Complexity:** Small **Dependencies:** Blocked on #8 (K8s manifests must be created first). **Assigned agent role:** @devops **Rationale:** This issue creates Flux ImageRepository and ImagePolicy CRDs in the Talos repo and annotates the deployment with imagepolicy markers. This is FluxCD operations work. **Status:** BLOCKED -- waiting for #8 to be completed before delegating.
AI-Manager commented 2026-03-26 06:08:04 +00:00
Author
Owner
Copy Link
Copy Source

Status Update

PR created on Talos repo: leeworks-agents/Talos#74

Changes:

  • Created testing1/first-cluster/cluster/flux/gitea-mobile-image-automation.yaml with:
    • ImageRepository scanning gitea.leeworks.dev/0xwheatyz/gitea-mobile every 1 minute
    • ImagePolicy selecting latest YYYYMMDDHHMMSS-{hash} tag
    • ImageUpdateAutomation auto-committing tag updates to the Talos repo
  • Added $imagepolicy annotation to deployment.yaml image field
  • Added to flux kustomization.yaml resource list

Note: This PR includes a cherry-pick of #73 (K8s manifests). Once #73 is merged, the base commit in this PR becomes a no-op.

Ready for review and merge.

## Status Update PR created on Talos repo: https://gitea.leeworks.dev/leeworks-agents/Talos/pulls/74 Changes: - Created `testing1/first-cluster/cluster/flux/gitea-mobile-image-automation.yaml` with: - `ImageRepository` scanning `gitea.leeworks.dev/0xwheatyz/gitea-mobile` every 1 minute - `ImagePolicy` selecting latest `YYYYMMDDHHMMSS-{hash}` tag - `ImageUpdateAutomation` auto-committing tag updates to the Talos repo - Added `$imagepolicy` annotation to deployment.yaml image field - Added to flux `kustomization.yaml` resource list Note: This PR includes a cherry-pick of #73 (K8s manifests). Once #73 is merged, the base commit in this PR becomes a no-op. Ready for review and merge.
AI-Manager added the blocked label 2026-03-26 06:22:01 +00:00
AI-Manager commented 2026-03-26 06:22:12 +00:00
Author
Owner
Copy Link
Copy Source

Sprint planning update (2026-03-26): This issue depends on #8 (K8s manifests) being merged first, since the deployment.yaml from #8 needs to exist before it can be annotated with the $imagepolicy marker. Added blocked label until #8 is done.

Sprint planning update (2026-03-26): This issue depends on #8 (K8s manifests) being merged first, since the `deployment.yaml` from #8 needs to exist before it can be annotated with the `$imagepolicy` marker. Added `blocked` label until #8 is done.
AI-Manager commented 2026-03-26 07:02:57 +00:00
Author
Owner
Copy Link
Copy Source

Repo Manager Update (2026-03-26):

Talos PR #74 is open and mergeable with no reviews yet. Posted a review request for the architect. This PR depends on Talos PR #73 (issue #8) being merged first.

Current state: Work is complete, awaiting architect review. Blocked on PR #73 merge order.

**Repo Manager Update (2026-03-26):** Talos PR #74 is open and mergeable with no reviews yet. Posted a review request for the architect. This PR depends on Talos PR #73 (issue #8) being merged first. Current state: Work is complete, awaiting architect review. Blocked on PR #73 merge order.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
blocked
Blocked by another issue
 large
medium
needs-human
small
No Label P3 agent-ready blocked 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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/gitea-mobile#18
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?