-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add comprehensive horizontal pod autoscaling documentation #3942
Conversation
docs/horizontal_pod_autoscaling.md
Outdated
--proxy-client-cert-file=<path to aggregator proxy cert> | ||
--proxy-client-key-file=<path to aggregator proxy key> | ||
``` | ||
* [kubernetes/kops#3679][4] - add config option to set `--horizontal-pod-autoscaler-use-rest-clients` kube-controller-manager flag required to enable custom metrics |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link name kubernetes/kops#3679
should be kubernetes/kops#3939
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 7625898.
docs/horizontal_pod_autoscaling.md
Outdated
Kops can assist in setting up HPA and recommends Kubernetes `>= 1.7` and Kops | ||
`>=1.8`. Relevant reading you will need to go through: | ||
|
||
* [Configure The Aggregation Layer][1]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No periods at the end looks nicer IMO.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 7772c44.
If we're breaking out HPA docs, can we link to it from here: https://github.com/kubernetes/kops/blob/master/docs/cluster_spec.md#kubecontrollermanager |
/ok-to-test |
@mikesplain yeah, there's some duplication 😓 ... both docs makes sense. I think your suggestion makes sense. |
/lgtm cancel |
Thinking about something. Does this feature use the api aggregation server? I know we have some nasty bugs in 1.8 that are being worked on |
@mikesplain addressed in c38aa8b.
@chrislovecnm yes it does. It's no problem. We can keep this open for discussion until everything has been resolved. |
@itskingori should we merge with a note about the bug, or just keep this open? thoughts? I am leaning toward keeping this open. |
/hold |
@chrislovecnm we can keep it open. I'm currently setting up HPA on 1.7 and can keep updating this as I roll it out). |
Any progress on this? What about custom metrics aggregator https://github.com/kubernetes/metrics/blob/master/IMPLEMENTATIONS.md ? Guess it still needs to be deployed. |
@chrislovecnm Any updates on this? I think it'd be good to get these docs in eventually. I believe the 1.8 bugs have since been resolved and this could be a good starting place for future HPA docs. Thoughts? |
@itskingori any other recommended updates since you last touched this? /assign |
@mikesplain Oh my, forgot about this. Learnt quite a bit, there's quite a bit to add. Will make some time tomorrow. |
Ping @itskingori :) Would love to get the docs updated with anything you've learned for 1.9! |
Oh that's why I got pinged, nevermind! |
@mikesplain yeah 😅 ... added some notes. I'm kinda torn in the sense that I don't want to regurgitate what's in the docs. So I've made mention of everything that's needed i.e. all the necessary configuration (from an implementation point of view), the cluster config that one needs and the metrics servers (resource and custom) that need to the registered (needs I'm wondering if having the manifest files for the metrics servers in kops as addons is a good idea or just send people to the relevant repos/docs. 🤔 And sorry for the delay, I promised this sooner. |
@mikesplain about this ... decided to create a separate PR, see #4581. |
This is great @itskingori! Thanks for all the detail! I agree that breaking that into a separate PR is a good call. cc: @chrislovecnm I think this looks good now if you want to take another look and consider removing the hold? /area documentation |
@chrislovecnm I never quite responded to your suggestion in #3942 (comment). I've addressed it in 929f299. @mikesplain added one last commit 🙈 post-LGTM. @23doors about #3942 (comment), addressed in 472604c. See also #4581. |
Awesome, good fix! /lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrislovecnm, itskingori, mikesplain The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
As requested by @chrislovecnm in #3939 (review).
Please note that this is a first pass. I'm currently trying to set up HPA and these are the things I've had to set. I'm yet to actually roll out the changes to the cluster and so I might update these docs with new discoveries.