You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the reverse lookup function added very recently and while it returns the correct result it always returns the node name as machine1.node.dc.consul even though we have a domain configured in server.json of blah, so I would expect the answer to be machine1.node.dc.blah
Firstly is my assumption correct? If so, I'll create a PR to update it.
Thanks
Finally just wanted to express my thanks/appreciation for consul as a whole. Great work.
The text was updated successfully, but these errors were encountered:
- The `config-checksum` annotation on the server-stateful and
client-daemonset would previously only updated on changes to their
respective extraConfig. This would fail to restart the server when ACL
config was updated. The behaviour has been updated to hash the entire
contents of the server/client config configmap so that any changes to
the configmap will force a recreate of the server/client pods. This will
allows consul upgrades to update an insecure install to a secure one.
I'm using the reverse lookup function added very recently and while it returns the correct result it always returns the node name as machine1.node.dc.consul even though we have a domain configured in server.json of blah, so I would expect the answer to be machine1.node.dc.blah
Firstly is my assumption correct? If so, I'll create a PR to update it.
Thanks
Finally just wanted to express my thanks/appreciation for consul as a whole. Great work.
The text was updated successfully, but these errors were encountered: