Migrate consul servers to puppet-on-k8s #563

Open
unkin-agent wants to merge 1 commits from benvin/puppet-migrate-consul into develop
Member

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
ci/woodpecker/pr/puppet-lint Pipeline was successful
ci/woodpecker/pr/erb-validate Pipeline was successful
ci/woodpecker/pr/bolt-validate Pipeline was successful
ci/woodpecker/pr/yamllint Pipeline was successful
ci/woodpecker/pr/epp-validate Pipeline was successful
ci/woodpecker/pr/puppet-validate Pipeline was successful
ci/woodpecker/pr/ruby-check Pipeline was successful
8678e907bc
Author
Member
  • 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.
All checks were successful
ci/woodpecker/pr/ruby-validate Pipeline was successful
Required
Details
ci/woodpecker/pr/puppet-lint Pipeline was successful
Required
Details
ci/woodpecker/pr/erb-validate Pipeline was successful
Required
Details
ci/woodpecker/pr/bolt-validate Pipeline was successful
Required
Details
ci/woodpecker/pr/yamllint Pipeline was successful
Required
Details
ci/woodpecker/pr/epp-validate Pipeline was successful
Required
Details
ci/woodpecker/pr/puppet-validate Pipeline was successful
Required
Details
ci/woodpecker/pr/ruby-check Pipeline was successful
Required
Details
This pull request can be merged automatically.
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/puppet-migrate-consul:benvin/puppet-migrate-consul
git checkout benvin/puppet-migrate-consul
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/puppet-prod#563