forward consul zone to k8s consul DNS LB #533

Open
unkin-agent wants to merge 1 commits from benvin/consul-dns-k8s into main
Member

Consul servers move into k8s (DC au-syd1) and the VMs retire, taking the 198.18.19.14 anycast route with them, so the resolvers' consul forward zone needs the k8s Consul DNS LoadBalancer instead.

  • point bind-internal fwd-consul forwarders at 198.18.200.5
  • update the upstreams comment

Requires a healthy k8s consul server (#531) first.

Consul servers move into k8s (DC au-syd1) and the VMs retire, taking the 198.18.19.14 anycast route with them, so the resolvers' consul forward zone needs the k8s Consul DNS LoadBalancer instead. - point bind-internal `fwd-consul` forwarders at 198.18.200.5 - update the upstreams comment Requires a healthy k8s consul server (#531) first.
unkin-agent added 1 commit 2026-10-09 23:01:54 +11:00
forward consul zone to k8s consul DNS LB
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/kubeconform Pipeline was successful
ff2309cc9f
Author
Member

No findings.

No findings.
All checks were successful
ci/woodpecker/pr/pre-commit Pipeline was successful
Required
Details
ci/woodpecker/pr/kubeconform Pipeline was successful
Required
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin benvin/consul-dns-k8s:benvin/consul-dns-k8s
git checkout benvin/consul-dns-k8s
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/argocd-apps#533