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

Migrate consul servers to puppet-on-k8s #563

Merged
benvin merged 1 commits from benvin/puppet-migrate-consul into develop 2026-11-08 18:00:40 +11:00
Conversation 1 Commits 1 Files Changed 1
+2
unkin-agent commented 2026-10-25 13:22:22 +11:00
Member
Copy Link
Copy Source

Consul servers build their peer list from a region-scoped PuppetDB query of their own role, so all members must report to the same PuppetDB and move to puppet-on-k8s together. syd1 clients use a static server list and are unaffected.

  • enable profiles::puppet::migrate for roles::infra::storage::consul
Consul servers build their peer list from a region-scoped PuppetDB query of their own role, so all members must report to the same PuppetDB and move to puppet-on-k8s together. syd1 clients use a static server list and are unaffected. - enable profiles::puppet::migrate for roles::infra::storage::consul
unkin-agent added 1 commit 2026-10-25 13:22:22 +11:00
Migrate consul servers to puppet-on-k8s
ci/woodpecker/pr/ruby-validate 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/bolt-validate Pipeline was successful
Details
ci/woodpecker/pr/yamllint 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 successful
Details
8678e907bc
unkin-agent commented 2026-10-25 13:23:48 +11:00
Author
Member
Copy Link
Copy Source
  • hieradata/roles/infra/storage/consul.yaml:6 — role-layer flip also moves drw1 consul servers, and drw1 clients still resolve servers via PuppetDB (members_lookup: true, common.yaml:239; static list is only in region/syd1.yaml) → state in the body that drw1 clients/servers are covered (or confirm drw1 servers stay visible to their PuppetDB after the move), since "syd1 clients are unaffected" does not address them.
- hieradata/roles/infra/storage/consul.yaml:6 — role-layer flip also moves drw1 consul servers, and drw1 clients still resolve servers via PuppetDB (`members_lookup: true`, common.yaml:239; static list is only in region/syd1.yaml) → state in the body that drw1 clients/servers are covered (or confirm drw1 servers stay visible to their PuppetDB after the move), since "syd1 clients are unaffected" does not address them.
benvin merged commit 7605623aa8 into develop 2026-11-08 18:00:40 +11:00
benvin deleted branch benvin/puppet-migrate-consul 2026-11-08 18:00:40 +11: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/puppet-prod#563
Delete Branch "benvin/puppet-migrate-consul"

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?