autoscaler
autoscaler copied to clipboard
Improve kwok provider installation docs
https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler/cloudprovider/kwok#how-to-use-kwok-provider talks about installing cluster-autoscaler in your local kind cluster but it doesn't clarify where to install the chart from:
Right now, it is implicitly assumed that the user is in the parent autoscaler directory. Many users will not have the repo cloned on their computer. The docs should be updated to use helm repo chart for installation.
/label area/provider/kwok /label cluster-autoscaler /label good-first-issue
@vadasambar: The label(s) /label area/provider/kwok , /label cluster-autoscaler , /label good-first-issue cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?
In response to this:
https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler/cloudprovider/kwok#how-to-use-kwok-provider talks about installing cluster-autoscaler in your local kind cluster but it doesn't clarify where to install the chart from:
Right now, it is implicitly assumed that the user is in the parent
autoscalerdirectory. Many users will not have the repo cloned on their computer. The docs should be updated to use helm repo chart for installation./label area/provider/kwok /label cluster-autoscaler /label good-first-issue
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Note that to use cluster-autoscaler with kwok provider needs a new cluster-autoscaler release (aka new official image). Added question around using latest tag based on master for the SIG meeting on 11th Dec 2023
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
/remove-lifecycle stale
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
/remove-lifecycle stale
@vadasambar, is there any update on this issue? IMO we can update the Kwok README.md