fix: allow argocd namespace ingress to forgejo #202
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-platform!202
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "200-forgejo-netpol-argocd"
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?
Summary
Changes
terraform/network-policies.tf: Added argocd namespace ingress rule tonetpol_forgejo, following the same pattern used by tailscale, woodpecker, and monitoring (and already present in the harbor policy)tofu plan Output
Providers not cached in this worktree so
tofu validatecould not run fully.tofu fmt -checkpassed clean. The change is a single ingress rule addition.Expected plan:
kubernetes_manifest.netpol_forgejowill be updated in-place with one additional ingress rule.Test Plan
tofu planshows only an in-place update tokubernetes_manifest.netpol_forgejoReview Checklist
Related Notes
pal-e-platform-- the project this work belongs toQA Review -- PR #202
Diff Analysis
terraform/network-policies.tf)The change adds a single ingress rule allowing the
argocdnamespace to reach pods in theforgejonamespace. The rule follows the exact same pattern as the existing tailscale, woodpecker, and monitoring rules in the same block, and matches how argocd is already referenced in the harbor network policy.Checklist
tofu fmt -checkpassedFindings
No issues found. This is a clean, minimal, pattern-consistent change.
VERDICT: APPROVE