-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
clusterapi: Add ephemeral disk capacity annotation for scale from zero #5416
clusterapi: Add ephemeral disk capacity annotation for scale from zero #5416
Conversation
…nts for scale from zero
this is a nice addition, thanks @cnmcavoy . i'll spend some time reviewing this week. |
i've created kubernetes-sigs/cluster-api#8036 to cover the docs update in cluster-api |
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.
this is a nice update and i think the additional annotation is not controversial for the cluster-api community. thanks again @cnmcavoy
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cnmcavoy, elmiko 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 |
to include latest changes to the annotation that are proposed in the cluster autoscaler. ref: kubernetes/autoscaler#5382 ref: kubernetes/autoscaler#5416
What type of PR is this?
/kind feature
What this PR does / why we need it:
Updates the clusterapi provider to support an additional capacity annotation for ephemeral disk capacity on MachineDeployments to supply information about the nodegroup shape.
Without an ephemeral disk capacity supplied, workloads that request ephemeral disk will not trigger a scale up of nodegroups with zero replicas as the ephemeral disk capacity defaults to zero bytes.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: