Skip to content
This repository was archived by the owner on Apr 17, 2019. It is now read-only.

Conversation

@fgrzadkowski
Copy link
Contributor

The new logic is the following:

  1. Take time of the newest node becoming available
  2. Reset status for PodScheduled condition to Unknown for all the pods with status True and reason Unschedulable with LastTransitionTime before timestamp from 1)
  3. Proceed only for newer unschedulable pods.

Ref: #25553

@fgrzadkowski
Copy link
Contributor Author

FYI I haven't tested this manually e2e.

Copy link
Contributor

Choose a reason for hiding this comment

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

typo: should be UnschedulablePodLister

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

@fgrzadkowski
Copy link
Contributor Author

All comments addressed. PTAL.

@piosz
Copy link
Contributor

piosz commented May 13, 2016

lgtm

@piosz piosz added the lgtm Indicates that a PR is ready to be merged. label May 13, 2016
@mwielgus mwielgus merged commit a835ece into kubernetes-retired:master May 13, 2016
mwielgus added a commit to kubernetes/autoscaler that referenced this pull request Apr 18, 2017
…se_pod_condition

[cluster-autoscaler] Add support for PodScheduled condition.
mwielgus added a commit to kubernetes/autoscaler that referenced this pull request Apr 18, 2017
…se_pod_condition

[cluster-autoscaler] Add support for PodScheduled condition.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants