unkin/puppet-prod
4
0
Fork 0
Code Issues 15 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

consul: point syd1 clients at k8s consul servers #550

Open
unkin-agent wants to merge 2 commits from benvin/consul-clients-k8s into develop
pull from: benvin/consul-clients-k8s
merge into: unkin:develop
Conversation 2 Commits 2 Files Changed 1
+7 -1
unkin-agent commented 2026-10-09 23:01:56 +11:00
Member
Copy Link
Copy Source

Hosts compiled in k8s can't look up consul servers in PuppetDB, so syd1 clients use a static join list, which now needs the k8s servers.

  • set consul_servers to the k8s LB IPs 198.18.200.11-.15
  • keep the five ausyd1nxvm2005-2009 names after them until the VM servers retire

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

Hosts compiled in k8s can't look up consul servers in PuppetDB, so syd1 clients use a static join list, which now needs the k8s servers. - set `consul_servers` to the k8s LB IPs 198.18.200.11-.15 - keep the five ausyd1nxvm2005-2009 names after them until the VM servers retire Requires a healthy k8s consul server (argocd-apps #531) first.
unkin-agent added 1 commit 2026-10-09 23:01:56 +11:00
consul: point syd1 clients at k8s consul servers
ci/woodpecker/pr/yamllint Pipeline was successful
Details
ci/woodpecker/pr/puppet-lint Pipeline was successful
Details
ci/woodpecker/pr/erb-validate Pipeline was successful
Details
ci/woodpecker/pr/ruby-validate Pipeline was successful
Details
ci/woodpecker/pr/bolt-validate Pipeline was successful
Details
ci/woodpecker/pr/epp-validate Pipeline was successful
Details
ci/woodpecker/pr/puppet-validate Pipeline was successful
Details
ci/woodpecker/pr/ruby-check Pipeline was canceled
Details
412771a766
unkin-agent commented 2026-10-09 23:05:19 +11:00
Author
Member
Copy Link
Copy Source
  • hieradata/country/au/region/syd1.yaml:12 — replacing the VM FQDNs makes every syd1 client (restarted by puppet-consul restart_on_change on this change, systemd Type=notify) depend solely on the k8s pods to join; with the StatefulSet at 1 replica, that pod being down at restart time leaves clients failing start (90s timeout, restart loop) while 5 VM servers are healthy → keep the five ausyd1nxvm200[5-9] FQDNs in the list alongside 198.18.200.11-15 and drop them in the VM-retirement PR
- hieradata/country/au/region/syd1.yaml:12 — replacing the VM FQDNs makes every syd1 client (restarted by puppet-consul `restart_on_change` on this change, systemd `Type=notify`) depend solely on the k8s pods to join; with the StatefulSet at 1 replica, that pod being down at restart time leaves clients failing start (90s timeout, restart loop) while 5 VM servers are healthy → keep the five `ausyd1nxvm200[5-9]` FQDNs in the list alongside 198.18.200.11-15 and drop them in the VM-retirement PR
unkin-agent added 1 commit 2026-10-09 23:06:12 +11:00
consul: keep VM servers in syd1 client join list
ci/woodpecker/pr/ruby-validate Pipeline was successful
Details
ci/woodpecker/pr/bolt-validate Pipeline was successful
Details
ci/woodpecker/pr/puppet-lint Pipeline was successful
Details
ci/woodpecker/pr/yamllint Pipeline was successful
Details
ci/woodpecker/pr/erb-validate Pipeline was successful
Details
ci/woodpecker/pr/epp-validate Pipeline was successful
Details
ci/woodpecker/pr/ruby-check Pipeline was successful
Details
ci/woodpecker/pr/puppet-validate Pipeline was successful
Details
64356b5e88
unkin-agent commented 2026-10-09 23:09:07 +11:00
Author
Member
Copy Link
Copy Source
  • PR description — change list says "disable members_lookup" but profiles::consul::client::members_lookup: false is already on develop (syd1.yaml:10, unchanged context) → drop that bullet
- PR description — change list says "disable `members_lookup`" but `profiles::consul::client::members_lookup: false` is already on develop (syd1.yaml:10, unchanged context) → drop that bullet
All checks were successful
ci/woodpecker/pr/ruby-validate Pipeline was successful
Required
Details
ci/woodpecker/pr/bolt-validate Pipeline was successful
Required
Details
ci/woodpecker/pr/puppet-lint Pipeline was successful
Required
Details
ci/woodpecker/pr/yamllint Pipeline was successful
Required
Details
ci/woodpecker/pr/erb-validate Pipeline was successful
Required
Details
ci/woodpecker/pr/epp-validate Pipeline was successful
Required
Details
ci/woodpecker/pr/ruby-check Pipeline was successful
Required
Details
ci/woodpecker/pr/puppet-validate 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-clients-k8s:benvin/consul-clients-k8s
git checkout benvin/consul-clients-k8s
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/puppet-prod#550
Delete Branch "benvin/consul-clients-k8s"

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?