Skip to content

Improve documentation of kubectl top #830

Open
@serathius

Description

@serathius

Due naming purpose of kubectl top is misinterpreted and compared to similarly named linux system tools. We should ensure that users understand meaning of those values and have proper expectation for this tool. Discussion: kubernetes-sigs/metrics-server#447

I propose to improve command help that would do better explanation and link to relevant documentation in Kubernetes docs.

We should explain or link to documentation explaining:

  • Where metrics come from
  • How they are calculated
  • How percentages are calculated
  • How they relate to HPA
  • When they should be used and why they shouldn't replace traditional tools and monitoring solutions

/sig instrumentation
/area kubectl
/kind feature

Metadata

Metadata

Assignees

Labels

area/kubectlhelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/backlogHigher priority than priority/awaiting-more-evidence.sig/cliCategorizes an issue or PR as relevant to SIG CLI.sig/instrumentationCategorizes an issue or PR as relevant to SIG Instrumentation.

Type

No type

Projects

Status

Needs Triage

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions