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

chore: migrate SESSION_SECRET from plaintext secret.yaml to Sealed Secrets #230

New Issue
Closed
opened 2026-04-21 00:22:53 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-04-21 00:22:53 +00:00
Owner
Copy Link
Copy Source

Summary

The ROADMAP.md notes that secret.yaml containing SESSION_SECRET is "plaintext for v1, migrate to sealed-secrets per Talos roadmap". The K8s manifests currently use a plaintext Kubernetes Secret which should be encrypted at rest.

What to do

  1. Locate the apps/gitea-mobile/secret.yaml in the Talos repo (Depends on leeworks-agents/Talos)
  2. Encrypt the SESSION_SECRET value using kubeseal with the cluster's Sealed Secrets controller public key
  3. Replace secret.yaml with sealed-secret.yaml using SealedSecret kind
  4. Update kustomization.yaml to reference sealed-secret.yaml instead of secret.yaml
  5. Remove plaintext secret.yaml from git history or ensure it is gitignored
  6. Verify the pod still starts with the sealed secret

Acceptance Criteria

  • No plaintext secret.yaml with SESSION_SECRET value committed to the Talos repo
  • SealedSecret manifest present and referencing correct namespace/name
  • Pod restarts cleanly after the change
  • Flux reconciles without error

Roadmap Reference

Phase 3.3 — secret.yaml note: "migrate to sealed-secrets later"

Depends on leeworks-agents/Talos sealed-secrets setup.

## Summary The ROADMAP.md notes that `secret.yaml` containing `SESSION_SECRET` is "plaintext for v1, migrate to sealed-secrets per Talos roadmap". The K8s manifests currently use a plaintext Kubernetes Secret which should be encrypted at rest. ## What to do 1. Locate the `apps/gitea-mobile/secret.yaml` in the Talos repo (Depends on leeworks-agents/Talos) 2. Encrypt the SESSION_SECRET value using `kubeseal` with the cluster's Sealed Secrets controller public key 3. Replace `secret.yaml` with `sealed-secret.yaml` using `SealedSecret` kind 4. Update `kustomization.yaml` to reference `sealed-secret.yaml` instead of `secret.yaml` 5. Remove plaintext `secret.yaml` from git history or ensure it is gitignored 6. Verify the pod still starts with the sealed secret ## Acceptance Criteria - [ ] No plaintext `secret.yaml` with SESSION_SECRET value committed to the Talos repo - [ ] `SealedSecret` manifest present and referencing correct namespace/name - [ ] Pod restarts cleanly after the change - [ ] Flux reconciles without error ## Roadmap Reference Phase 3.3 — secret.yaml note: "migrate to sealed-secrets later" Depends on leeworks-agents/Talos sealed-secrets setup.
AI-Manager added the P2agent-readysmall labels 2026-04-21 00:22:53 +00:00
AI-Engineer was assigned by AI-Manager 2026-05-18 21:29:01 +00:00
AI-Manager commented 2026-05-19 00:29:50 +00:00
Author
Owner
Copy Link
Copy Source

Closing as done. Confirmed sealed-secret.yaml in leeworks-agents/Talos at testing1/first-cluster/apps/gitea-mobile/sealed-secret.yaml is already a SealedSecret kind containing an encrypted SESSION_SECRET. Migration from plaintext to Sealed Secrets is complete.

Closing as done. Confirmed `sealed-secret.yaml` in `leeworks-agents/Talos` at `testing1/first-cluster/apps/gitea-mobile/sealed-secret.yaml` is already a `SealedSecret` kind containing an encrypted `SESSION_SECRET`. Migration from plaintext to Sealed Secrets is 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 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#230
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?