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

Research and implement a MVP for cluster autoscaling #45

Open
3 tasks
Darkness4 opened this issue Jun 26, 2022 · 0 comments
Open
3 tasks

Research and implement a MVP for cluster autoscaling #45

Darkness4 opened this issue Jun 26, 2022 · 0 comments
Assignees
Labels
area/k0s Related to k0s and k0sctl/cfctl features. kind/enhancement Indicates new feature requests. S1 High impact on the end user ; this issue must be addressed as soon as possible. status/acknowledged Issue has been taken in account by the core team, but no planning is set.

Comments

@Darkness4
Copy link
Collaborator

Darkness4 commented Jun 26, 2022

Let's focus on Exoscale and a single availability group first.

There are multiple solutions, but this is my proposition. The idea is based on Slurm cloud-bursting. We need to solve two problems:

  1. How to spawn VM which will join a private network? The private repository with Ansible can help us.
  2. How to make the VM join the cluster? cfctl could be the answer.

Therefore, we should combine these two features. Because cfctl is similar to our Ansible.

To add more details, here is the join mechanism for k0s:

  1. On a controller node, call k0s token create --role=worker, this will create a join token. For extra security, the token must have an expiration time: k0s token create --role=worker --expiry=1h.
  2. On the new virtual machine, via SSH, install k0s and call sudo k0s install worker --token-file /path/to/token/file.
  3. Then start: sudo k0s start.

Ejecting a node is also easy: Cordon + Drain + Kubectl delete node. Then delete the VM.

This feature will certainly take time.

@Darkness4 Darkness4 added kind/enhancement Indicates new feature requests. area/k0s Related to k0s and k0sctl/cfctl features. labels Jun 26, 2022
@Darkness4 Darkness4 added S1 High impact on the end user ; this issue must be addressed as soon as possible. status/acknowledged Issue has been taken in account by the core team, but no planning is set. labels Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/k0s Related to k0s and k0sctl/cfctl features. kind/enhancement Indicates new feature requests. S1 High impact on the end user ; this issue must be addressed as soon as possible. status/acknowledged Issue has been taken in account by the core team, but no planning is set.
Development

No branches or pull requests

2 participants