-
Notifications
You must be signed in to change notification settings - Fork 828
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for the "kubectl top" command across multiple clusters #5058
Comments
Solution 1: Modify the resource request response of the Modification:
Impact on Users:
|
Solution 2: Replace Modification:
Impact on Users: |
Solution 3: Use the top command provided by
|
I shared this topic at today's community meeting. The comments were that solutions 1 and 2 have a direct impact on user behavior and are not recommended. Solution 3 is recommended. |
We have added component fleet-apiserver, which provides users with APIs compatible with the Kubernetes single cluster experience. Related proposal PR #4317
For most
kubectl
commands, we can obtain the same experience as that of a single Kubernetes cluster.Currently, for the
kubectl top
command, there is a phenomenon:As we can see, the number of resources obtained has doubled. We want to obtain the format of the lower part, but there is no related resource(cpu/memory) use data.
This is because for
PodMetrics
andNodeMetirics
resources, requests are forwarded to thekarmada-metrics-adapter
component for processing. The difference is that thekarmada-metrics-adapter
component is not processed in the same way asfleet-apiserver
(adding the suffix .clusterspacce.{cluster-name} to resources).The text was updated successfully, but these errors were encountered: