feat(devnet-4): expose watchtower HTTP API for gated rollouts#8
Open
barnabasbusa wants to merge 2 commits into
Open
feat(devnet-4): expose watchtower HTTP API for gated rollouts#8barnabasbusa wants to merge 2 commits into
barnabasbusa wants to merge 2 commits into
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, so images only roll when explicitly triggered). - dns_server.yaml: add watchtower-<host> A/AAAA records for ethereum_node hosts. - all.sops.yaml: add secret_watchtower_api_token.
d2d9d7b switched to `python -m pip install` under the asdf-shimmed python but never reshimmed afterwards, so the pip-installed ansible-lint console script had no shim and CI failed with `ansible-lint: command not found` (exit 127). Add `asdf reshim python` after the install. Also normalize the watchtower container env block to 2-space indentation to match the rest of the file.
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.This 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 — which is the whole point of gated rollouts.Changes
all.yaml— addethereum_node_watchtower_prefix/ethereum_node_watchtower_hostname(alongsidebn-/rpc-); put the watchtower container on the shared network and setVIRTUAL_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.all.sops.yaml— addsecret_watchtower_api_token.Notes
/v1/update(no fork). Bearer-auth only on that vhost.https://watchtower-<host>.srv.glamsterdam-devnet-4.ethpandaops.io/v1/updateauthenticates with the token and triggers a scan.