From f961ef45c8b194c3d7ad7574a73605826fba1bef Mon Sep 17 00:00:00 2001 From: Simon Mayer Date: Thu, 30 Jan 2025 12:45:49 +0100 Subject: [PATCH] Update README --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c145f6e..f18a52f 100644 --- a/README.md +++ b/README.md @@ -56,7 +56,7 @@ metalctl network allocate --description "" --name --project A firewall needs to be created with appropriate firewall rules. An example can be found at [firewall-rules.yaml](capi-lab/firewall-rules.yaml). ```bash -metalctl firewall create --description --name --hostname --project --partition --image --size --firewall-rules-file= --networks internet,$(shell metalctl network list --name -o template --template '{{ .id }}') +metalctl firewall create --description --name --hostname --project --partition --image --size --firewall-rules-file= --networks internet,$(metalctl network list --name -o template --template '{{ .id }}') ``` For your first cluster, it is advised to start with our generated template. @@ -113,6 +113,10 @@ EOF Additionally, the `metal-ccm` has to be deployed for the machines to reach `Running` phase. For this use the [template](capi-lab/metal-ccm.yaml) and fill in the required variables. +```bash +cat capi-lab/metal-ccm.yaml | envsubst | kubectl --kubeconfig capms-cluster.kubeconfig apply -f - +``` + If you want to provide service's of type `LoadBalancer` through MetalLB by the `metal-ccm`, you need to deploy MetalLB: ```bash