fix: allow argocd namespace ingress to Harbor #161
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!161
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "148-harbor-argocd-netpol"
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
ArgoCD Image Updater needs to reach Harbor to check for new image tags. The Harbor NetworkPolicy was missing
argocdfrom its ingress allowlist, causing connection timeouts.Changes
terraform/network-policies.tf: Addedargocdnamespace tonetpol_harboringress rules alongside existing tailscale, harbor, monitoring, and woodpecker entries.Test Plan
tofu apply -target=kubernetes_manifest.netpol_harborkubectl get networkpolicy -n harbor default-deny-ingress -o yamlincludes the argocd namespace selectorReview Checklist
Related
Review: LGTM
Diff: +1 line, 1 file changed. Minimal and correct.
Findings:
argocdingress rule follows the exact samenamespaceSelectorpattern as the existing tailscale, harbor, monitoring, and woodpecker entries. Consistent.netpol_harborresource only.No issues found. Ready for merge.