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: fix constraints for non-default clusters (ENT) #19449

Merged
merged 1 commit into from
Dec 12, 2023

Conversation

tgross
Copy link
Member

@tgross tgross commented Dec 12, 2023

The Connect-related constraints injected by the Connect job mutating hook do not account for non-default consul blocks (for Nomad Enterprise). This works when both the default and non-default clusters are available and are the same version, but not when they do not.

Fixes: #19442

@pkazmierczak
Copy link
Contributor

I think we're missing a changelog entry?

The Connect-related constraints injected by the Connect job mutating hook do not
account for non-default `consul` blocks (for Nomad Enterprise). This works when
both the default and non-default clusters are available and are the same
version, but not when they do not.

Fixes: #19442
@tgross tgross force-pushed the b-consul-constraints-non-default-cluster branch from 6159c0f to e543630 Compare December 12, 2023 16:28
@tgross tgross added the backport/1.7.x backport to 1.7.x release line label Dec 12, 2023
@tgross tgross merged commit a76daf6 into main Dec 12, 2023
21 checks passed
@tgross tgross deleted the b-consul-constraints-non-default-cluster branch December 12, 2023 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.7.x backport to 1.7.x release line theme/consul theme/enterprise Issues related to Enterprise features type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consul constraints don't use non-default Consul cluster (ENT)
2 participants