Closed sftim closed 8 months ago
/triage accepted /priority important-longterm /help
@sftim: This request has been marked as needing help from a contributor.
Please ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help
command.
I would like to work on this issue @sftim /assign
Should I Make a new file inside Workloads!! In 1 PR I will be creating 2 topics like (HorizontalPodAutoscaler, VerticalPodAutoscaler) and will it be sufficient, because It will be taking 2-3 PR's!
For advice on how to contribute to the Kubernetes docs, please ask in #sig-docs on the Kubernetes Slack workspace. If you're not already a member of that workspace, you can visit https://slack.k8s.io/ for an invitation.
Anyone is welcome to work on this issue.
@kumarankit999 it's slightly unhelpful to assign an issue to yourself and also to ask questions about how to work on it; ideally, people only assign an issue once they are confident that they know how to resolve it.
Our no cookie-licking policy means that anyone is welcome to open a PR that closes an open issue. It's still friendly to reach out to people who might already be working on the same thing.
See https://www.redhat.com/en/blog/dont-lick-cookie for an explanation of the jargon.
Thanks @sftim, I was just asking it. I can fix this issue!
Hey @sftim! This has been pending for more than a month. So, May I go ahead and create a PR?
I have a basic markdown structure for autoscaling.md
file is ready and I can add more details as needed after raising a PR.
PRs are welcome, and because this project is open source, nobody needs permission.
In light of our policy on cookie licking: /unassign @kumarankit999
I think we'll make progress better without any assignee. If anyone wants to share that they have started work, feel free to open a draft pull request that mentions this issue.
This is a Feature Request
What would you like to be added Within https://kubernetes.io/docs/concepts/workloads/, add a new and brief page that has an overview of autoscaling. This means adding a new Markdown file.
The new page should mention:
HorizontalPodAutoscaler
VerticalPodAutoscaler
Cluster proportional autoscaler
Karpenter (aim to make it clear that this is a thing that autoscales nodes, not Pods)
Cluster autoscaler (aim to make it clear that this is a thing that autoscales nodes, not Pods)
Optionally, also mention:
For this issue, all that's needed is a few words about each item. Later PRs could add more detail.
Why is this needed
Comments This helps with https://github.com/kubernetes/website/issues/4493 /language en /kind feature
PS. I didn't mark this as a good first issue. However, if you're looking for something to work on, and haven't already contributed to Kubernetes' docs, there may be some issues available marked as good first issues. See this issue query page. If you have already worked on an issue, please leave these for people who are new to contributing.