Repository navigation
fix: restore metrics-server access to cluster kubelets - #65
Merged
Merged
Conversation
Contributor
Terraform Format and Style 🖌
|
Contributor
Terraform Format and Style 🖌
|
Contributor
Terraform Format and Style 🖌
|
Contributor
Terraform Format and Style 🖌
|
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.
Summary
Diagnosis
Four cloud nodes are Ready, but both telemetry and the Kubernetes metrics API return only k8s-node-1. Metrics-server runs on k8s-node-1 and repeatedly times out scraping the other three cloud nodes at their public IPs on TCP 10250. The live Hetzner firewall is attached to all four nodes and has no matching allowance; its unrestricted internal rule only covers 10.0.0.0/16.
Impact and rollout
This is an additive firewall permission change. No pod or node restarts are required. No infrastructure changes have been applied locally. Review the Terraform plan before merging: the intended change is an in-place update to hcloud_firewall.k8s_cluster adding this rule, with no removals, replacements, or attachment changes. Metrics-server retries every 15 seconds and telemetry refreshes every 30 seconds.
Validation
Post-deployment verification
Tracking
bd ready --json failed because the local Dolt journal is reported corrupt. No database repair was attempted; a bd task ID could not be created.