search

kubernetes / autoscaler

Autoscaling components for Kubernetes
Apache License 2.0
7.81k stars 3.87k forks source link

Cluster Autoscaler: document Node autoscaling in official k8s docs #6646

Open towca opened 3 months ago

towca commented 3 months ago

Which component are you using?: Cluster Autoscaler

Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:

Official Kubernetes documentation doesn't document Node autoscaling at all. It would be beneficial for Kubernetes users to be able to read about core Node autoscaling concepts without having to look for that separately.

Describe the solution you'd like.:

Add a "Node autoscaling" page to the concepts/cluster-administration section of Kubernetes docs. The page would explain core Node autoscaling concepts, and point to the officially supported Node autoscalers (Cluster Autoscaler and Karpenter).

sftim commented 3 months ago

https://github.com/kubernetes/website/pull/45197 has added a page about cluster autoscaling.

I think this is done. /close

k8s-ci-robot commented 3 months ago

@sftim: Closing this issue.

In response to [this](https://github.com/kubernetes/autoscaler/issues/6646#issuecomment-2018191298): >https://github.com/kubernetes/website/pull/45197 has added a page about cluster autoscaling. > >I think this is done. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
MaciekPytel commented 3 months ago

/reopen As I commented in https://github.com/kubernetes/website/pull/45197#issuecomment-2018308592, we are committed to a broader alignment effort between Cluster Autoscaler and Karpenter as well as providing in-depth documentation of similarities, differences and portability challenges between the two projects. This goes far beyond the documentation introduced in https://github.com/kubernetes/website/pull/45197:

k8s-ci-robot commented 3 months ago

@MaciekPytel: Reopened this issue.

In response to [this](https://github.com/kubernetes/autoscaler/issues/6646#issuecomment-2018320106): >/reopen >As I commented in https://github.com/kubernetes/website/pull/45197#issuecomment-2018308592, we are committed to a broader alignment effort between Cluster Autoscaler and Karpenter as well as providing in-depth documentation of similarities, differences and portability challenges between the two projects. This goes far beyond the documentation introduced in https://github.com/kubernetes/website/pull/45197: > * We want to agree on core autoscaling concepts and bring both projects towards that alignement (as opposed to just documenting current state). > * We want to highlight shared APIs, similarities and what level of compatibility the users should expect when moving between clusters managed by CA and Karpenter. > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
sftim commented 3 months ago

If you want to transfer this to k/website, we have a Prow command for that (/transfer website)

Bryce-Soghigian commented 3 months ago

Would be great to include karpenter in our efforts to have a unifed experience of switching between karpenter + CAS

MaciekPytel commented 3 months ago

Involving Karpenter team has been a plan all along and we've already discussed it with @jonathan-innis @ellistarn and other when Karpenter first joined the sig (context links: doc summarising earlier discussions, sig-autoscaling update I did with @jonathan-innis discussing this).

I consider an explicit approval from Karpenter team and sig-autoscaling leads a requirement for any of the related efforts (docs update, re-naming proposed in a different issue, etc).

k8s-triage-robot commented 1 week ago

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

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

You can:

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

/lifecycle stale

towca commented 1 week ago

The https://github.com/kubernetes/website/pull/45802 PR adding the documentation is in review. The review has stalled a bit, I bumped it for the reviewers during the sig-autoscaling meeting today.

/remove-lifecycle stale