fix(monitoring): isolate Talos etcd metrics - #36
Merged
Conversation
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
Talos etcd metrics can now be collected without making port 2381 reachable from ordinary workloads or LAN clients. The Grafana metrics collector scrapes the three control planes directly, while Cilium blocks every other Pod from initiating a connection to the etcd metrics port.
The Omni helper applies the Talos listener and control-plane-only ingress rule. Apply it only after Argo has synchronized the Cilium policy, then reboot each control plane one at a time as required by Talos.
Validation
python3 scripts/validate.pybash -n omni/scripts/apply-etcd-metrics.sh