-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
docs: known issue with v2dns SRV requests #21331
Conversation
It is impossible to resolve the individual service addresses. | ||
This can affect Nomad installations, where the Service Address field is always specified to Consul. | ||
Setting `experiments: [ "v1dns" ]` in the agent configuration will revert to the old behavior. | ||
A fix will be present in a future release of Consul 1.19.1 [[GH-21325](https://github.com/hashicorp/consul/issues/21325)]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A fix will be present in a future release of Consul 1.19.1 [[GH-21325](https://github.com/hashicorp/consul/issues/21325)]. | |
A fix will be included in Consul 1.19.1 [[GH-21325](https://github.com/hashicorp/consul/issues/21325)]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor suggestions to improve the description.
Co-authored-by: Jeff Boruszak <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With that change it LGTM!
Approved on behalf of consul-docs
Description
Document known issues related to #21325