feat: expose watchtower HTTP API for gated rollouts#171
Open
barnabasbusa wants to merge 2 commits into
Open
Conversation
Expose each node's watchtower HTTP API at a watchtower-<host> vhost (same nginx-proxy pattern as bn-/rpc-) so panda-pulse's /roll command can trigger gated, sequential image rollouts over HTTPS with a bearer token — no SSH. - all.yaml: add ethereum_node_watchtower_prefix/_hostname; put watchtower on the shared network with VIRTUAL_HOST/VIRTUAL_PORT/LETSENCRYPT_HOST + the API token env; switch from --interval=900 (auto-poll) to --http-api-update (trigger-only). - dns_server.yaml: add watchtower-<host> A/AAAA records for ethereum_node hosts. Each devnet created from this template must add secret_watchtower_api_token to its all.sops.yaml.
The setup script installs ansible-lint via `python -m pip install` under the asdf-shimmed python but never reshims afterwards, so the console script has no shim and CI fails with `ansible-lint: command not found`. Add `asdf reshim python` after the install. Also: add the watchtower API token secret reference, normalize the watchtower env block to 2-space indentation, and fix a malformed `#noqa` (missing space) on the inventory-web role vars that 24.6.0 rejects as both yaml[comments] and unsuppressed var-naming.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expose each node's watchtower HTTP API at a
watchtower-<host>vhost (the same nginx-proxy pattern asbn-/rpc-), so panda-pulse's/rollcommand can trigger gated, sequential image rollouts over HTTPS with a bearer token — no SSH. Mirrors ethpandaops/glamsterdam-devnets#8 in the template so new devnets get it by default.Also switches watchtower from
--interval=900(auto-poll) to--http-api-update(trigger-only): images no longer roll on a timer, only when explicitly triggered.Changes
all.yaml— addethereum_node_watchtower_prefix/_hostname; put the watchtower container on the shared network withVIRTUAL_HOST/VIRTUAL_PORT/LETSENCRYPT_HOST+WATCHTOWER_HTTP_API_TOKEN; replace--interval=900with--http-api-update.dns_server.yaml— addwatchtower-<host>A/AAAA records forethereum_nodehosts.Note
Each devnet created from this template must add
secret_watchtower_api_tokento itsall.sops.yaml.