devnet-6: retire the xatu-experimental cannon#32
Merged
Conversation
The per-devnet cannon stamped by mca-xatu-devnets in the platform repo replaced this one: it coordinates against the devnet's own xatu server and writes canonical data directly to clickhouse-raw's glamsterdam-devnet-6 database. This chart still pointed at the retired xatu-experimental pipeline on an image that cannot decode Gloas blocks, so it derived nothing while hammering the beacon load balancer.
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
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.
The platform's mca-xatu-devnets now stamps a per-devnet cannon (utility cluster) that coordinates against the devnet's own xatu server and writes canonical data directly to clickhouse-raw's glamsterdam-devnet-6 database, so the k8s cannon here — still pointed at retired xatu-experimental on an image that can't decode Gloas blocks — is redundant and derives nothing. Disable it; xatu-mimicry/cl-mimicry cutover is a separate follow-up.