From 0aaa28d5df3f384986f5eb086c43720ae4211fdc Mon Sep 17 00:00:00 2001 From: "Joshua M. Boniface" Date: Fri, 25 Oct 2024 02:32:22 -0400 Subject: [PATCH] Try backticks --- docs/deployment/getting-started.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/deployment/getting-started.md b/docs/deployment/getting-started.md index da866ce..1406caa 100644 --- a/docs/deployment/getting-started.md +++ b/docs/deployment/getting-started.md @@ -94,6 +94,7 @@ You will also need a switch to connect the nodes, capable of vLAN trunks passing 0. In your local repository, edit the `hosts` file and add a new cluster. How you do so is technically up to you, but for those without advanced Ansible experience, the following format is simplest: + ``` --- # First cluster [cluster1] @@ -106,7 +107,7 @@ You will also need a switch to connect the nodes, capable of vLAN trunks passing hv1.cluster2.mydomain.tld hv2.cluster2.mydomain.tld hv3.cluster2.mydomain.tld - + ``` ❕ **NOTE** The hostnames given here must be the actual reachable FQDNs of the hypervisor nodes in the "upstream" network; if they do not resolve in DNS, you can use the `ansible_host=` per-entry variable to set the IP address in the "upstream" network for each node.