unkin/argocd-apps
3
0
Fork 0
Code Issues 7 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

TEMP: forward k8s.syd1.au.unkin.net to external external-dns service #269

Merged
benvin merged 1 commits from benvin/resolvers-k8s-externaldns-temp into main 2026-07-21 00:14:03 +10:00
Conversation 0 Commits 1 Files Changed 1
+12 -3
unkinben commented 2026-07-21 00:12:01 +10:00
Owner
Copy Link
Copy Source

The bind-resolvers openforwarder view forwarded k8s.syd1.au.unkin.net to the in-cluster bind-externaldns (198.18.200.8), which is not reliably serving those records yet, so lookups return NXDOMAIN.

Concrete impact: Gitea cannot resolve the k8s-hosted CI host, so its outbound webhook fails and tagged releases never trigger CI (e.g. cutting a new bind-operator release from a tag).

This points the fwd-k8s-syd1-au-unkin-net forwarder at the existing external external-dns bind service anycast 198.18.19.20 (puppet roles::infra::dns::externaldns — master ausyd1nxvm2127 + slaves 2128/2129, advertised via OSPF), which still holds the working k8s.syd1.au.unkin.net records. It is in the same 198.18.19.0/24 anycast family as the consul forwarder (198.18.19.14) the resolvers already use, so it is reachable from the pods.

Temporary measure. Revert to 198.18.200.8 once external-dns publishes to the in-cluster bind-externaldns service. Only the forward target changes; no CRD/schema changes.

The bind-resolvers `openforwarder` view forwarded `k8s.syd1.au.unkin.net` to the in-cluster bind-externaldns (198.18.200.8), which is not reliably serving those records yet, so lookups return NXDOMAIN. Concrete impact: Gitea cannot resolve the k8s-hosted CI host, so its outbound webhook fails and tagged releases never trigger CI (e.g. cutting a new bind-operator release from a tag). This points the `fwd-k8s-syd1-au-unkin-net` forwarder at the existing external external-dns bind service anycast **198.18.19.20** (puppet `roles::infra::dns::externaldns` — master `ausyd1nxvm2127` + slaves `2128`/`2129`, advertised via OSPF), which still holds the working `k8s.syd1.au.unkin.net` records. It is in the same 198.18.19.0/24 anycast family as the consul forwarder (198.18.19.14) the resolvers already use, so it is reachable from the pods. Temporary measure. Revert to 198.18.200.8 once external-dns publishes to the in-cluster bind-externaldns service. Only the forward target changes; no CRD/schema changes.
unkinben added 1 commit 2026-07-21 00:12:01 +10:00
Temporarily forward k8s.syd1.au.unkin.net to external external-dns 34e8c80d49 
The bind-resolvers forwarded k8s.syd1.au.unkin.net to the in-cluster
bind-externaldns (198.18.200.8), which is not reliably serving those
records yet, so lookups return NXDOMAIN. Notably Gitea cannot resolve the
k8s CI host, so its webhook fails and tagged releases (e.g. bind-operator)
never trigger CI.

Point the forwarder at the existing external external-dns bind service
anycast (198.18.19.20, puppet roles::infra::dns::externaldns), which still
holds the working records. Temporary; revert to 198.18.200.8 once
external-dns publishes to the in-cluster service.
benvin merged commit 7ee5dfbbcd into main 2026-07-21 00:14:03 +10:00
benvin deleted branch benvin/resolvers-k8s-externaldns-temp 2026-07-21 00:14:03 +10:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
benvin (BenVincent) unkin-agent (Unkin Agent) unkinben (Ben Vincent)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/argocd-apps#269
Delete Branch "benvin/resolvers-k8s-externaldns-temp"

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?