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

consul/connect: use additional constraints in scheduling connect tasks #10702

Merged
merged 1 commit into from
Jun 4, 2021

Commits on Jun 3, 2021

  1. consul/connect: use additional constraints in scheduling connect tasks

    This PR adds two additional constraints on Connect sidecar and gateway tasks,
    making sure Nomad schedules them only onto nodes where Connect is actually
    enabled on the Consul agent.
    
    Consul requires `connect.enabled = true` and `ports.grpc = <number>` to be
    explicitly set on agent configuration before Connect APIs will work. Until
    now, Nomad would only validate a minimum version of Consul, which would cause
    confusion for users who try to run Connect tasks on nodes where Consul is not
    yet sufficiently configured. These contstraints prevent job scheduling on nodes
    where Connect is not actually use-able.
    
    Closes #10700
    shoenig committed Jun 3, 2021
    Configuration menu
    Copy the full SHA
    c90471d View commit details
    Browse the repository at this point in the history