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

Jump to bottom

Use Service Placement Constraints in Enforcer #2857

Merged
merged 1 commit into from
May 20, 2019
Merged

Use Service Placement Constraints in Enforcer #2857

merged 1 commit into from
May 20, 2019

Commits on May 17, 2019

  1. Use Service Placement Constraints in Enforcer 

    This patch updates the ConstraintEnforcer to use the placement
constraints from the current service spec rather than the placement
constraints from the current task spec because they may be outdated
in some cases (e.g., when the service was previously updated to
modify placement constrainst but the node to which the task was
scheduled still satisfies the constraints. If the node is updated
in a way which causes it to no longer satisfy the new constraints
then the task should be removed even if it still would satisfy the
original task constraints).

Docker-DCO-1.1-Signed-off-by: Josh Hawn <[email protected]> (github: jlhawn)
    Josh Hawn committed May 17, 2019
    Configuration menu
    Copy the full SHA
    b39ccd7 View commit details
    Browse the repository at this point in the history