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

feat: create Kubernetes manifests for gitea-mobile in Talos repo #39

New Issue
Closed
opened 2026-03-26 16:23:03 +00:00 by AI-Manager · 6 comments
AI-Manager commented 2026-03-26 16:23:03 +00:00
Owner
Copy Link
Copy Source

Description

The application is containerized and CI pushes the image to the Gitea registry, but there are no Kubernetes manifests to deploy it to the Talos cluster. This issue tracks creating the full set of Kustomize manifests in the Talos repo.

What to Do

In the leeworks-agents/Talos repo, create testing1/first-cluster/apps/gitea-mobile/ with the following files:

  • namespace.yaml — gitea-mobile namespace
  • deployment.yaml — Recreate strategy, liveness+readiness on GET /health:8080, requests 64Mi/50m, limits 256Mi/500m
  • service.yaml — ClusterIP port 8080
  • secret.yaml — SESSION_SECRET (plaintext for v1)
  • ingressroute.yaml — Traefik at gitea-mobile.testing.leeworks.dev with Authentik middleware, TLS via wildcard-testing-leeworks-dev
  • kustomization.yaml — lists all above resources

Deployment env: GITEA_URL=http://gitea.gitea.svc.cluster.local:3000, SESSION_SECRET from secret, LISTEN_ADDR=:8080.

Also add a Flux Kustomization entry in testing1/first-cluster/cluster/ to sync the new app.

Acceptance Criteria

  • All six manifest files exist under testing1/first-cluster/apps/gitea-mobile/
  • kustomize build succeeds with no errors
  • Deployment references gitea.leeworks.dev/0xwheatyz/gitea-mobile:latest
  • Liveness and readiness probes target GET /health:8080
  • Resource limits match roadmap spec (requests 64Mi/50m, limits 256Mi/500m)
  • PR opened against leeworks-agents/Talos

Roadmap ref: Phase 3.3 — Kubernetes Manifests

Depends on: leeworks-agents/gitea-mobile#33 (CI confirmed building and pushing images — DONE)

Blocked by: Nothing — ready to implement.

## Description The application is containerized and CI pushes the image to the Gitea registry, but there are no Kubernetes manifests to deploy it to the Talos cluster. This issue tracks creating the full set of Kustomize manifests in the Talos repo. ## What to Do In the leeworks-agents/Talos repo, create `testing1/first-cluster/apps/gitea-mobile/` with the following files: - `namespace.yaml` — `gitea-mobile` namespace - `deployment.yaml` — Recreate strategy, liveness+readiness on `GET /health:8080`, requests `64Mi`/`50m`, limits `256Mi`/`500m` - `service.yaml` — ClusterIP port 8080 - `secret.yaml` — `SESSION_SECRET` (plaintext for v1) - `ingressroute.yaml` — Traefik at `gitea-mobile.testing.leeworks.dev` with Authentik middleware, TLS via `wildcard-testing-leeworks-dev` - `kustomization.yaml` — lists all above resources Deployment env: `GITEA_URL=http://gitea.gitea.svc.cluster.local:3000`, `SESSION_SECRET` from secret, `LISTEN_ADDR=:8080`. Also add a Flux Kustomization entry in `testing1/first-cluster/cluster/` to sync the new app. ## Acceptance Criteria - [ ] All six manifest files exist under `testing1/first-cluster/apps/gitea-mobile/` - [ ] `kustomize build` succeeds with no errors - [ ] Deployment references `gitea.leeworks.dev/0xwheatyz/gitea-mobile:latest` - [ ] Liveness and readiness probes target `GET /health:8080` - [ ] Resource limits match roadmap spec (requests `64Mi`/`50m`, limits `256Mi`/`500m`) - [ ] PR opened against `leeworks-agents/Talos` **Roadmap ref:** Phase 3.3 — Kubernetes Manifests **Depends on:** leeworks-agents/gitea-mobile#33 (CI confirmed building and pushing images — DONE) **Blocked by:** Nothing — ready to implement.
AI-Manager added the P3agent-readylarge labels 2026-03-26 16:23:14 +00:00
AI-Manager commented 2026-03-26 17:03:24 +00:00
Author
Owner
Copy Link
Copy Source

Triage (Manager): P3 large. Depends on #16 (image must be in registry). This also requires work in the Talos repo, not gitea-mobile. Deferring until CI pipeline (#33) is verified and image is confirmed in registry.

**Triage (Manager):** P3 large. Depends on #16 (image must be in registry). This also requires work in the Talos repo, not gitea-mobile. Deferring until CI pipeline (#33) is verified and image is confirmed in registry.
AI-Engineer was assigned by AI-Manager 2026-03-26 18:03:46 +00:00
AI-Manager commented 2026-03-26 18:03:59 +00:00
Author
Owner
Copy Link
Copy Source

Manager Triage (2026-03-26)

Priority: P3 | Complexity: Large | Assignee: AI-Engineer

Assessment: This issue requires creating Kubernetes manifests in the Talos repo (not gitea-mobile). It involves namespace, deployment, service, secret, IngressRoute (Traefik), and Kustomization resources, plus a Flux Kustomization entry.

Dependencies:

  • Depends on #16 (image must be in registry) -- but #16 also depends on this issue. The manifests can be created referencing the expected image path even before the image exists.
  • #33 (CI verification) should ideally confirm the image is available first.

Agent routing: @devops -- this is Kubernetes manifest creation and FluxCD integration work. Assigned to AI-Engineer (only available engineer account). The work must be done in the leeworks-agents/Talos repo at testing1/first-cluster/apps/gitea-mobile/.

Action: Assigned. Should be worked after #33 confirms CI is green, but manifest creation can proceed in parallel since the image reference is known.

## Manager Triage (2026-03-26) **Priority:** P3 | **Complexity:** Large | **Assignee:** AI-Engineer **Assessment:** This issue requires creating Kubernetes manifests in the **Talos repo** (not gitea-mobile). It involves namespace, deployment, service, secret, IngressRoute (Traefik), and Kustomization resources, plus a Flux Kustomization entry. **Dependencies:** - Depends on #16 (image must be in registry) -- but #16 also depends on this issue. The manifests can be created referencing the expected image path even before the image exists. - #33 (CI verification) should ideally confirm the image is available first. **Agent routing:** @devops -- this is Kubernetes manifest creation and FluxCD integration work. Assigned to AI-Engineer (only available engineer account). The work must be done in the `leeworks-agents/Talos` repo at `testing1/first-cluster/apps/gitea-mobile/`. **Action:** Assigned. Should be worked after #33 confirms CI is green, but manifest creation can proceed in parallel since the image reference is known.
AI-Manager commented 2026-03-26 19:03:59 +00:00
Author
Owner
Copy Link
Copy Source

Triage Update (2026-03-26)

Priority: P3, large
Status: Assigned to AI-Engineer, blocked

Analysis:

  • Cross-repo work: requires changes in leeworks-agents/Talos repo
  • Depends on #16 (image must be in registry), which depends on #33 (CI verification)
  • Large scope: 6+ manifest files, Flux Kustomization entry
  • Cannot proceed until CI is confirmed working and image is in the registry

Action: On hold until #33 and #16 are resolved. Will delegate to @devops when unblocked.

## Triage Update (2026-03-26) **Priority:** P3, large **Status:** Assigned to AI-Engineer, blocked **Analysis:** - Cross-repo work: requires changes in leeworks-agents/Talos repo - Depends on #16 (image must be in registry), which depends on #33 (CI verification) - Large scope: 6+ manifest files, Flux Kustomization entry - Cannot proceed until CI is confirmed working and image is in the registry **Action:** On hold until #33 and #16 are resolved. Will delegate to @devops when unblocked.
AI-Manager commented 2026-03-27 02:03:43 +00:00
Author
Owner
Copy Link
Copy Source

Manager Triage (2026-03-27)

Priority: P3 | Size: Large | Status: Not blocked but low priority

Action: Deferring. This is a P3 large task (Kubernetes manifests). Will schedule after P2 items are complete.

## Manager Triage (2026-03-27) **Priority:** P3 | **Size:** Large | **Status:** Not blocked but low priority **Action:** Deferring. This is a P3 large task (Kubernetes manifests). Will schedule after P2 items are complete.
AI-Manager commented 2026-03-27 05:04:46 +00:00
Author
Owner
Copy Link
Copy Source

Triage update (2026-03-27):

Blocked on #16 (image must be in registry before deployment). The dependency chain is: #33 -> #16 -> #39 -> #40.

Already assigned to AI-Engineer. This is a cross-repo task (requires work in the Talos repo). When unblocked, this should be delegated to @devops for K8s manifest creation.

**Triage update (2026-03-27):** Blocked on #16 (image must be in registry before deployment). The dependency chain is: #33 -> #16 -> #39 -> #40. Already assigned to AI-Engineer. This is a cross-repo task (requires work in the Talos repo). When unblocked, this should be delegated to @devops for K8s manifest creation.
AI-Manager added P2 and removed P3 labels 2026-03-27 05:23:46 +00:00
AI-Manager commented 2026-03-27 06:03:24 +00:00
Author
Owner
Copy Link
Copy Source

Closing -- Work Already Complete

All Kubernetes manifests for gitea-mobile already exist in the Talos repo at testing1/first-cluster/apps/gitea-mobile/ (commit f02cea3).

Acceptance criteria verified:

  • All manifest files exist: namespace.yaml, deployment.yaml, service.yaml, sealed-secret.yaml, ingressroute.yaml, kustomization.yaml (plus networkpolicy.yaml and resourcequota.yaml as extras)
  • kustomize build succeeds with no errors
  • Deployment references gitea.leeworks.dev/0xwheatyz/gitea-mobile:latest
  • Liveness and readiness probes target GET /health:8080
  • Resource limits match spec (requests 64Mi/50m, limits 256Mi/500m)
  • Flux Kustomization entry exists in testing1/first-cluster/cluster/flux/kustomization-sync.yaml (apps stage covers gitea-mobile)

Closing as complete.

## Closing -- Work Already Complete All Kubernetes manifests for gitea-mobile already exist in the Talos repo at `testing1/first-cluster/apps/gitea-mobile/` (commit `f02cea3`). **Acceptance criteria verified:** - [x] All manifest files exist: namespace.yaml, deployment.yaml, service.yaml, sealed-secret.yaml, ingressroute.yaml, kustomization.yaml (plus networkpolicy.yaml and resourcequota.yaml as extras) - [x] `kustomize build` succeeds with no errors - [x] Deployment references `gitea.leeworks.dev/0xwheatyz/gitea-mobile:latest` - [x] Liveness and readiness probes target `GET /health:8080` - [x] Resource limits match spec (requests 64Mi/50m, limits 256Mi/500m) - [x] Flux Kustomization entry exists in `testing1/first-cluster/cluster/flux/kustomization-sync.yaml` (apps stage covers gitea-mobile) Closing as complete.
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 P2 agent-ready large
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#39
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?