Add Golang-based deploy-cli which handles bmo and ironic deployments

Signed-off-by: Max Rantil <max.rantil@est.tech>

Signed-off-by: Huy Mai <huy.mai@est.tech>

Makefile

@@ -193,6 +193,10 @@ $(CONTROLLER_GEN): hack/tools/go.mod
 $(KUSTOMIZE): hack/tools/go.mod
 	cd hack/tools; go build -o $(abspath $@) sigs.k8s.io/kustomize/kustomize/v5
 
+.PHONY: deploy-cli
+deploy-cli:
+	cd hack/tools/deploy-cli; go build -o ../../../tools/bin/deploy-cli
+
 .PHONY: build-e2e
 build-e2e:
 	cd test; go build ./...

config/README.md

@@ -3,6 +3,32 @@
 This folder contains kustomizations for the Baremetal Operator. They have
 traditionally been used through the [deploy.sh](../tools/deploy.sh) script,
 which takes care of generating the necessary config for basic-auth and TLS.
+
+Experimentally, in `deploy.sh` stead, you can use the new golang-based 
+[deploy-cli](../hack/tools/deploy-cli) library,
+which, at the moment, handles everything `deploy.sh` does. You can either:
+- Run the package with `go run`:
+
+```shell
+cd $BMO_ROOT/hack/tools/deploy-cli
+go run *.go
+```
+
+- Otherwise, build the package to a static binary:
+
+```shell
+cd $BMO_ROOT
+make deploy-cli
+```
+
+And run the binary with:
+
+```shell
+./tools/bin/deploy-cli -h
+```
+
+To check which options are available, run the script/binary with `-h`.
+
 However, a more GitOps friendly way would be to create your own static overlay.
 Check the `overlays/e2e` for an example that is used in the e2e tests.
 In the CI system we generate the necessary credentials before starting the test

hack/tools/deploy-cli/.gitignore

@@ -0,0 +1 @@
+deploy-cli