kemko/nomad
1
0
Fork 0
mirror of https://github.com/kemko/nomad.git synced 2026-01-01 16:05:42 +03:00
Code Issues Packages Projects Releases Wiki Activity

e2e: mention in the terraform readme that we require a local Consul binary (#25944)

Browse Source
This commit is contained in:
Piotr Kazmierczak
2025-05-28 17:12:57 +02:00
committed by GitHub
parent 5dd880ad61
commit a10c2f6de7
1 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
e2e/terraform/README.md
View File

@@ -56,14 +56,18 @@ client_count_linux = "4"
client_count_windows_2016 = "1"
```
You will also need a Consul Enterprise license file and a Nomad Enterprise license file.
You will also need a Consul Enterprise license file and a Nomad Enterprise
license file, and a local Consul binary to provision Consul.
Optionally, edit the `nomad_local_binary` variable in the
`terraform.tfvars` file to change the path to the local binary of
Nomad you'd like to upload, but keep in mind it has to match the OS and the CPU architecture of the nodes (amd64 linux).
Optionally, edit the `nomad_local_binary` variable in the `terraform.tfvars`
file to change the path to the local binary of Nomad you'd like to upload, but
keep in mind it has to match the OS and the CPU architecture of the nodes (amd64
linux).
NOTE: If you want to have a cluster with mixed CPU architectures, you need to specify the count and also provide the
corresponding binary using `var.nomad_local_binary_client_ubuntu_jammy` and or `var.nomad_local_binary_client_windows_2016`.
NOTE: If you want to have a cluster with mixed CPU architectures,
you need to specify the count and also provide the corresponding
binary using `var.nomad_local_binary_client_ubuntu_jammy` and or
`var.nomad_local_binary_client_windows_2016`.
Run Terraform apply to deploy the infrastructure: