Skip to content
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 the cluster-autoscaler addon #5869

Merged
merged 11 commits into from
Oct 9, 2020

Conversation

xmudrii
Copy link
Member

@xmudrii xmudrii commented Sep 15, 2020

What this PR does / why we need it:

This PR adds the cluster-autoscaler addon.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Part of #3642

Documentation:

TBD once implemented in the UI.

Does this PR introduce a user-facing change?:

Add the cluster-autoscaler addon

@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 15, 2020
@toschneck
Copy link
Member

@xmudrii it would be good also to document the usage of the addon.

The cluster-autoscaler manifest has been fetched from
https://github.com/kubernetes/autoscaler/blob/d97e3dc221e0143d7b0541f1012be994560b35f2/cluster-autoscaler/cloudprovider/clusterapi/examples/deployment.yaml

The manifest doesn't work out of the box. Required changes are made in
follow-up commits.
No additional changes to resources were made in this commit
The ClusterRole used in the original Cluster-API provider example
manifest is lacking some roles causing cluster-autoscaler to show
a bunch of warnings.

This ClusterRole has been copied from the AWS provider example manifest.
https://github.com/kubernetes/autoscaler/blob/63259fb5dd89baeb2a46b5b3b27ba6578066166e/cluster-autoscaler/cloudprovider/aws/examples/cluster-autoscaler-autodiscover.yaml#L10-L83

It's also used by some other providers as well.

The original ClusterRole was also using
rbac.authorization.k8s.io/v1beta1 instead of
rbac.authorization.k8s.io/v1.
@xmudrii xmudrii changed the title [WIP] Add the cluster-autoscaler addon Add the cluster-autoscaler addon Oct 9, 2020
@kubermatic-bot kubermatic-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 9, 2020
Copy link
Contributor

@xrstf xrstf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Oct 9, 2020
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 6474ac28a2672042a8ed84ee700ca0740e1d60d1

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xmudrii, xrstf

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@xmudrii
Copy link
Member Author

xmudrii commented Oct 9, 2020

@toschneck This is only the initial PR to add the manifest. There are some changes required on the API/UI side, so we'll document it once everything is complete.

@kubermatic-bot kubermatic-bot merged commit 41d6e75 into kubermatic:master Oct 9, 2020
@xmudrii xmudrii deleted the cluster-autoscaler-addon branch October 9, 2020 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants