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

Backport of consul: set partition for gateway config entries into release/1.8.x #22408

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #22228 to be assessed for backporting due to the inclusion of the label backport/1.8.x.

The below text is copied from the body of the original PR.


When we write Connect gateway configuation entries from the server, we're not passing in the intended partition. This means we're using the server's own partition to submit the configuration entries and this may not match. Note this requires the Nomad server's token has permission to that partition.

Also, move the config entry write after we check Sentinel policies. This allows us to return early if we hit a Sentinel error without making Consul RPCs first.

Ref: https://hashicorp.atlassian.net/browse/NET-9529


Overview of commits

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/consul-partition-for-gateway-config-entries/evenly-fond-akita branch from 639aae1 to 47102f1 Compare May 29, 2024 20:32
@tgross tgross merged commit 4f40612 into release/1.8.x May 29, 2024
18 of 19 checks passed
@tgross tgross deleted the backport/consul-partition-for-gateway-config-entries/evenly-fond-akita branch May 29, 2024 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants