Should have a way to print all supported modes and available params about cluster-proportional-autoscaler HOT 19 OPEN

How would this work, someone would docker run the container with a different entrypoint with the help flags? It is true that it would be good to build the help into the package, but the mechanism to access the help text seems a little obscure.

from cluster-proportional-autoscaler.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from cluster-proportional-autoscaler.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

from cluster-proportional-autoscaler.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

from cluster-proportional-autoscaler.

@fejta-bot: Closing this issue.

from cluster-proportional-autoscaler.

/lifecycle frozen

from cluster-proportional-autoscaler.

/good-first-issue

from cluster-proportional-autoscaler.

@bowei:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

from cluster-proportional-autoscaler.

@bowei is this issue is to update help file wo show all this option and related information ?

from cluster-proportional-autoscaler.

/assign

from cluster-proportional-autoscaler.

@bowei i am planning to include argument option in command which will display corresponding text file content
for example:
cluster-proportional-autoscaler --show-modes
this will invoke content of text file containing all modes and its information.

from cluster-proportional-autoscaler.

@bowei
Please suggest.

from cluster-proportional-autoscaler.

@bowei friendly reminder

from cluster-proportional-autoscaler.

/remove-lifecycle frozen

from cluster-proportional-autoscaler.

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

from cluster-proportional-autoscaler.

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

from cluster-proportional-autoscaler.

/remove-lifecycle rotten

from cluster-proportional-autoscaler.

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

from cluster-proportional-autoscaler.

/remove-lifecycle stale

from cluster-proportional-autoscaler.