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

scaleutils: protect Autoscaler node from scale in. #198

Merged
merged 1 commit into from Jul 1, 2020

Conversation

jrasell
Copy link
Member

@jrasell jrasell commented Jul 1, 2020

Until the Nomad Autoscaler has the ability to reconcile actions
which have not reached a terminal state, the scaleutils should
protect the node the Nomad Autoscaler is running on from scalein
actions. This gives better assurance that the autoscaler wont
drain the node its on and then not be able to complete the scaling
action.

Even once the autoscaler has reconcile ability, there are some
interesting dicussions to be had about what logic to apply in the
situation where the autoscaler is running as a Nomad job and
identifies its own node for scaling in. In this case, we know it
will never be fully able to complete the action.

@jrasell jrasell added this to the 0.1.0 milestone Jul 1, 2020
@jrasell jrasell self-assigned this Jul 1, 2020
Copy link
Contributor

@cgbaker cgbaker left a comment

Choose a reason for hiding this comment

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

some questions about error handling

helper/scaleutils/nomad.go Show resolved Hide resolved
helper/scaleutils/nomad.go Show resolved Hide resolved
Until the Nomad Autoscaler has the ability to reconcile actions
which have not reached a terminal state, the scaleutils should
protect the node the Nomad Autoscaler is running on from scalein
actions. This gives better assurance that the autoscaler wont
drain the node its on and then not be able to complete the scaling
action.

Even once the autoscaler has reconcile ability, there are some
interesting dicussions to be had about what logic to apply in the
situation where the autoscaler is running as a Nomad job and
identifies its own node for scaling in. In this case, we know it
will never be fully able to complete the action.
@jrasell jrasell force-pushed the protect-autoscaler-node-cluster-scaling branch from 1c7117b to 8148308 Compare July 1, 2020 12:59
@jrasell jrasell merged commit 2a8e110 into master Jul 1, 2020
@jrasell jrasell deleted the protect-autoscaler-node-cluster-scaling branch July 1, 2020 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants