From 479d6e68620e7d24b92ab5a8b83631903da2e9f6 Mon Sep 17 00:00:00 2001 From: Ranjandas Date: Tue, 2 Mar 2021 09:44:35 +1100 Subject: [PATCH] Added references to node name --- .../docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx b/website/content/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx index 468988c465..e8d7c43721 100644 --- a/website/content/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx +++ b/website/content/docs/k8s/installation/multi-cluster/vms-and-kubernetes.mdx @@ -57,7 +57,7 @@ $ consul tls cert create -server -dc=vm-dc -node ==> Saved vm-dc-server-consul-0-key.pem ``` --> Note the `node` option in the above command. This is a [requirement](https://www.consul.io/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#tls) for Consul Federation to work. Alternatively, if you plan to use the same certificate and key pair on all your Consul server nodes, use `-node "*"` instead. +-> Note the `-node` option in the above command. This should be same as the node name of the [Consul Agent](https://www.consul.io/docs/agent#running-an-agent). This is a [requirement](https://www.consul.io/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#tls) for Consul Federation to work. Alternatively, if you plan to use the same certificate and key pair on all your Consul server nodes, or you don't know the nodename in advance, use `-node "*"` instead. See the help for output of `consul tls cert create -h` to see more options for generating server certificates.