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 Rancher as a cloud provider #4041

Closed
wants to merge 8 commits into from
Closed

Conversation

douglasmakey
Copy link

Hello Kubernetes Community,

We are the Ubisoft Kubernetes Team: @douglasmakey, @patrickdappollonio, and @promagne. We worked during the past couple of months alongside Rancher (and now Suse) to implement a Node Autoscaler based on the Rancher software as a cloud provider, and we're sending it here for broader community use.

It has the basic support you would expect, like increasing and decreasing node groups and configuring using a ConfigMap.

We're here if you have any questions!

@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
  • Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Apr 27, 2021
@k8s-ci-robot
Copy link
Contributor

Welcome @douglasmakey!

It looks like this is your first PR to kubernetes/autoscaler 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/autoscaler has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Apr 27, 2021
@k8s-ci-robot k8s-ci-robot requested review from Jeffwan and towca April 27, 2021 18:30
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Apr 27, 2021
Copy link
Contributor

@mwielgus mwielgus left a comment

Choose a reason for hiding this comment

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

Please update the main readme as well so.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 3, 2021
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 25, 2021
@douglasmakey
Copy link
Author

Please update the main readme as well so.

Done, thanks @mwielgus

@douglasmakey douglasmakey requested a review from mwielgus May 26, 2021 14:33
@reylejano
Copy link
Member

/assign @aleksandra-malinowska @feiskyer

Copy link
Member

@feiskyer feiskyer left a comment

Choose a reason for hiding this comment

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

Could you also add an OWNERS file in the new rancher directory?

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: douglasmakey, feiskyer

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 27, 2021
@k8s-ci-robot k8s-ci-robot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label May 27, 2021
@douglasmakey
Copy link
Author

Could you also add an OWNERS file in the new rancher directory?

Done, thanks @feiskyer

@douglasmakey
Copy link
Author

@douglasmakey can you please remove the OWNERS file from this PR?

Hi @leodotcloud, sure, I will remove the file.

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Oct 1, 2021
access=token-abcdef
secret=ksjdhfiusdhfkjsdfhisudhfnskjdfhskjdfhksdjfhksjdfhksdjf
cluster-id=c-abcdef
autoscaler_node_arg: "2:6:c-abcdef:np-abcde"
Copy link
Contributor

Choose a reason for hiding this comment

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

minor: new line

@@ -0,0 +1,118 @@
apiVersion: rbac.authorization.k8s.io/v1
Copy link
Contributor

Choose a reason for hiding this comment

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

seems it ends with txt. is it used for rendering templates?


// GetAvailableGPUTypes return all available GPU types cloud provider supports.
func (u rancherProvider) GetAvailableGPUTypes() map[string]struct{} {
return availableGPUTypes
Copy link
Contributor

Choose a reason for hiding this comment

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

is this supported in rancher platform? Seems it's an empty map?


```
docker push rancher/cluster-autoscaler:dev
```
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you add some information about contacts of maintainers here?

It would be helpful for maintainers to reach out to the cloud provider owners for release coordination when necessary.

@Jeffwan
Copy link
Contributor

Jeffwan commented Oct 1, 2021

@leodotcloud I help review non-rancher codes and please take a look.

@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Oct 19, 2021
@k8s-ci-robot
Copy link
Contributor

@douglasmakey: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 25, 2021
@xrl
Copy link

xrl commented Nov 19, 2021

How is this going? We'd love to use it with our rancher infrastructure.

@reylejano
Copy link
Member

@douglasmakey please rebase

@xrl
Copy link

xrl commented Nov 19, 2021

I am having some issues setting up this code on a new rancher-controlled cluster. I bet my token is wrong but this stacktrace is pretty nasty: https://gist.github.com/xrl/e7caf2e45048aa71b0d489267741c251

Holler if you want more of it, it's dumping all the goroutine stacks. I just went ahead and put in the full log before I try and fix things.

@k8s-triage-robot
Copy link

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

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 17, 2022
@patrickdappollonio
Copy link

Hey all!

Just for transparency purposes, both @douglasmakey and myself -- the two people running this PR -- have left Ubisoft since and moved on to new adventures. Back then, I think we were lacking some of the support from Rancher to have this merged.

As such, we might be able to contribute some extra time but it would be better if Ubisoft/Rancher takes ownership instead... Speaking for both Douglas and myself, happy if either wants to take over the PR to have it merged.

Hope that helps with expectations regarding whether this will be merged or not!

@leodotcloud
Copy link

@patrickdappollonio Thank you for the note, I am in a similar situation too.

Bringing this to your attention @cjellick, @deniseschannon, @jambajaar, @cloudnautique.

@leodotcloud
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 17, 2022
@mwielgus
Copy link
Contributor

Closed due to inactivity. Feel free to reopen.

@mwielgus mwielgus closed this May 17, 2022
@glermaidt
Copy link

Please re-open. We really need this.

@patrickdappollonio
Copy link

Unfortunately, unless someone wants to take it from here, neither @douglasmakey nor I still work at the previous company where this was our goal.

@cambierr
Copy link

cambierr commented Jun 3, 2022 via email

@glermaidt
Copy link

@cambierr - This sounds fantastic! - Could you provide mere deets? And you said OSS. Am I to presume it will be open-sourced?

@cambierr
Copy link

cambierr commented Jun 5, 2022 via email

@rodcloutier
Copy link

We, at Ubisoft, will work with Rancher to re-open this MR.

@ctrox
Copy link
Contributor

ctrox commented Jun 15, 2022

An bit of a coincidence @rodcloutier, you wrote this just a few hours before we got ready to post our RKE2 autoscaler implementation (see PR linked above). This PR here contains an implementation for RKE1, RKE2 provisioning in Rancher was not even a thing back then. Were you planning on adding support for RKE1 or RKE2?

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. area/cluster-autoscaler cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.