1 Issue closed by 2 people

• The command `autoscale deployment` should provide a flag for providing the maximum, average memory utilization

  #1481 closed Jun 25, 2025

11 Unresolved conversations

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• Add a way to print the current kubectl command argument string in a reusable way for kuberctl

  #1748 commented on Jun 25, 2025 • 0 new comments

• Fall back from PATCH to PUT on `apply` and `edit`

  #1351 commented on Jun 25, 2025 • 0 new comments

• kubectl apply is slow due to client side throttling

  #1722 commented on Jun 25, 2025 • 0 new comments

• Add `proxy-url` command line option

  #1655 commented on Jun 25, 2025 • 0 new comments

• Add support for kubectl rollout restart --all --all-namespaces

  #1751 commented on Jun 25, 2025 • 0 new comments

• `kubectl get --ignore-not-found` behavior unclear

  #1596 commented on Jun 25, 2025 • 0 new comments

• `kubectl describe` sometimes shows memory in millibytes

  #1597 commented on Jun 26, 2025 • 0 new comments

• Improve documentation of kubectl top

  #830 commented on Jun 27, 2025 • 0 new comments

• The resources.limits.memory unit is automatically converted. Why cannot the unit be displayed as configured?

  #1729 commented on Jun 27, 2025 • 0 new comments

• Ability To Send Custom Headers From kubectl

  #1352 commented on Jul 1, 2025 • 0 new comments

• Support for setting resourceVersion in kubectl get

  #965 commented on Jul 1, 2025 • 0 new comments