cli-experimental icon indicating copy to clipboard operation
cli-experimental copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

autoscale : unknown command "hpa" for "kubectl"

Open ibnjunaid opened this issue 2 years ago • 9 comments

On the kubectl documentation page its written that we can also use kubectl hpa (-f FILENAME | TYPE NAME | TYPE/NAME) [--min=MINPODS] --max=MAXPODS [--cpu-percent=CPU] to create horizontal pod autoscalers but when I tried to run the command I got the following message error: unknown command "hpa" for "kubectl" Did you mean this? cp

Following is my output of kubectl version Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647", GitTreeState:"clean", BuildDate:"2023-05-17T14:20:07Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"linux/amd64"} Kustomize Version: v5.0.1 Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.1", GitCommit:"4c9411232e10168d7b050c49a1b59f6df9d7ea4b", GitTreeState:"clean", BuildDate:"2023-05-12T19:03:40Z", GoVersion:"go1.20.3", Compiler:"gc", Platform:"linux/amd64"}

Is this is a typo in the documentation page or there is supposed to be a kubectl hpa command.

ibnjunaid avatar Jul 08 '23 10:07 ibnjunaid

I checked and the error is there. It is not present in the code as well , it can be an upcoming feature/enhancement. It is supposed to be like autoscale alias more than whole new command so adding one in kubectl/autoscale.go will help

Ritikaa96 avatar Jul 13 '23 05:07 Ritikaa96

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jan 24 '24 09:01 k8s-triage-robot

I think this is an error if there is no discussion of making it a command . WDYT /sig cli

Ritikaa96 avatar Jan 24 '24 10:01 Ritikaa96

/remove-lifecycle stale

Ritikaa96 avatar Jan 31 '24 09:01 Ritikaa96

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Apr 30 '24 09:04 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar May 30 '24 09:05 k8s-triage-robot

This issue is worth a discussion/review /remove-lifecycle rotten

Ritikaa96 avatar Jun 13 '24 10:06 Ritikaa96