fix: configure metrics-server for EKS host networking#284
Merged
Conversation
metrics-server was deployed with default Helm values, which fails on EKS because pod networking cannot reach the kubelet metrics endpoint on port 10250. This configures: - hostNetwork.enabled: true — runs in the node network namespace so metrics-server can reach kubelets directly - containerPort: 4443 — avoids port conflict with the kubelet already bound to 10250 on the host - --kubelet-preferred-address-types=InternalIP — resolves nodes by internal IP, which is more reliable on EKS Applied to both the Go (HelmChart CR for workload clusters) and Python (Pulumi Helm Release for control room) deployment paths. Enables `kubectl top` on EKS clusters.
Control room clusters use the AWS VPC-CNI, where pod traffic originates from node ENIs with the same security groups — so metrics-server can reach kubelet:10250 without hostNetwork. Only workload clusters (which use Calico overlay networking) need this fix.
amdove
approved these changes
Apr 30, 2026
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
2 participants
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
kubectl topfails on EKS workload clusters with "Metrics API not available" because metrics-server can't scrape kubelet metrics (connection timeout on port 10250)hostNetwork.enabled: true— runs in the node network namespace, bypassing the Calico overlaycontainerPort: 4443— avoids port conflict with kubelet already bound to 10250 on the host--kubelet-preferred-address-types=InternalIP— resolves nodes by internal IP on EKSTest plan
kubectl top podsandkubectl top nodesreturn metrics