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.

Sign up for GitHub

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

Document elastic cluster scaling down #41

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Document elastic cluster scaling down #41

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e74afc1
Document elastic cluster scaling down
guillaumeeb Oct 19, 2022
a3b060d
Apply suggestions from code review
guillaumeeb Oct 19, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions EGI.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -365,6 +365,20 @@ Then, you'll need to restart clues2 service:
service cluesd restart
```

#### Why cluster is not scaling down?

CLUES will only delete VMs that are _"idle"_: i.e. with __no running pods__.

You can use `kubectl` commands to see which pods are running on nodes:
guillaumeeb marked this conversation as resolved.
Show resolved Hide resolved

```bash
sudo kubectl get nodes # get the list of nodes
kubectl describe nodes vnode-4.localdomain # shows the list of pods running on vnode-4
guillaumeeb marked this conversation as resolved.
Show resolved Hide resolved
```

Keep also in mind that if you have configured a minimum number of free nodes,
the same number of idle nodes will be maintained.

### Daskhub without EGI Check-in auth and less limits

If you don't want to go through the step of configuring EGI Check-in auth
Expand Down