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

UPSTREAM: <carry>: openshift: Move MaxNodesTotalReached event #102

Merged

Conversation

frobware
Copy link

@frobware frobware commented Jun 5, 2019

This moves the location of where the event is emitted from by reverting PR #90 and emitting the event during scale-up.

Emit MaxNodesTotalReached in scale up when the condition is reached.
@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jun 5, 2019
…from frobware/add-cluster-size-reached-event"

This reverts commit 9b2cf49, reversing
changes made to 291cdcd.
@frobware
Copy link
Author

frobware commented Jun 5, 2019

/refresh

@frobware
Copy link
Author

frobware commented Jun 5, 2019

/retest

@@ -295,9 +295,7 @@ func (a *StaticAutoscaler) RunOnce(currentTime time.Time) errors.AutoscalerError
klog.V(1).Info("No unschedulable pods")
} else if a.MaxNodesTotal > 0 && len(readyNodes) >= a.MaxNodesTotal {
scaleUpStatus.Result = status.ScaleUpNoOptionsAvailable

Choose a reason for hiding this comment

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

Let the Result also be filled by ScaleUp() and totally omit this else if. WDYT?

Copy link
Author

@frobware frobware Jun 6, 2019

Choose a reason for hiding this comment

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

I don't really want to change existing behaviour. All I want is the event emitted when the cluster can scale up no more. I'm hoping that's the smaller, simplest and most discrete change particularly as we want to carry our change from rebase to rebase.

Choose a reason for hiding this comment

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

I am fine if you want to take care of event part only. Though i think it wont change behavior if we move the filling up Result to the ScaleUp, leave it to you to decide whether to include in this PR or not.

@vikaschoudhary16
Copy link

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 6, 2019
@openshift-merge-robot openshift-merge-robot merged commit ee51cfd into openshift:master Jun 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants