-
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
Fix TLS cert creation instruction for Consul federation #9838
Conversation
The Server certificates used for Federation require the node name in the form of `<node>.server.<dc>.<domain>`. Not having this would through `bad tls certificate` error. * Fixed cert create command * Added note to create a wildcard cert (like the ones on Kubernetes) * Fixed numbering
🤔 This PR has changes in the |
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.
Looks great!
Should you provide an example of the error when you don't pass -node
?
Thank you for reviewing. Sure, will update the doc with the error message. |
@lkysow If you are happy with the change (added error message), I will merge the PR (provided I have access to merge). |
Looks great! |
lmk if you can't merge |
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/342092. |
🍒✅ Cherry pick of commit 86b2a2b onto |
Fix TLS cert creation instruction for Consul federation
🍒✅ Cherry pick of commit 86b2a2b onto |
Fix TLS cert creation instruction for Consul federation
Fix TLS cert creation instruction for Consul federation
The Consul Federation requires the Server nodes to have an additional SAN entry of the form
<node_name>.server.<dc>.<domain>
. This was missing from the instructions for K8S to VM federation.