fix #5

Author: sp-yduck

.gitignore

@@ -25,8 +25,7 @@ Dockerfile.cross
 *.swo
 *~
 
-
 *_test.go
 
-# 
-config/samples/secret.yaml
+# release
+out

Makefile

@@ -11,6 +11,9 @@ else
 GOBIN=$(shell go env GOBIN)
 endif
 
+GOARCH  := $(shell go env GOARCH)
+GOOS    := $(shell go env GOOS)
+
 # Setting SHELL to bash allows bash commands to be executed by recipes.
 # Options are set to exit when a recipe line exits non-zero or a piped command fails.
 SHELL = /usr/bin/env bash -o pipefail
@@ -58,6 +61,16 @@ vet: ## Run go vet against code.
 test: manifests generate fmt vet envtest ## Run tests.
 	KUBEBUILDER_ASSETS="$(shell $(ENVTEST) use $(ENVTEST_K8S_VERSION) --bin-dir $(LOCALBIN) -p path)" go test ./... -coverprofile cover.out
 
+CLUSTER_NAME := cappx-test
+
+.PHONY: create-workload-cluster
+create-workload-cluster: $(KUSTOMIZE) $(ENVSUBST) $(KUBECTL)
+	export CLUSTER_NAME=$(CLUSTER_NAME) && $(KUSTOMIZE) build templates | $(ENVSUBST) | $(KUBECTL) apply -f -
+
+.PHONY: delete-workload-cluster
+delete-workload-cluster: $(KUBECTL)
+	$(KUBECTL) delete cluster $(CLUSTER_NAME)
+
 ##@ Build
 
 .PHONY: build
@@ -72,7 +85,7 @@ run: manifests generate fmt vet ## Run a controller from your host.
 # (i.e. docker build --platform linux/arm64 ). However, you must enable docker buildKit for it.
 # More info: https://docs.docker.com/develop/develop-images/build_enhancements/
 .PHONY: docker-build
-docker-build: test ## Build docker image with the manager.
+docker-build: # test ## Build docker image with the manager.
 	docker build -t ${IMG} .
 
 .PHONY: docker-push
@@ -119,6 +132,30 @@ deploy: manifests kustomize ## Deploy controller to the K8s cluster specified in
 undeploy: ## Undeploy controller from the K8s cluster specified in ~/.kube/config. Call with ignore-not-found=true to ignore resource not found errors during deletion.
 	$(KUSTOMIZE) build config/default | kubectl delete --ignore-not-found=$(ignore-not-found) -f -
 
+##@ Release
+
+## Location to output for release
+RELEASE_DIR := out
+$(RELEASE_DIR):
+	mkdir -p $(RELEASE_DIR)
+
+# RELEASE_TAG := $(shell git describe --abbrev=0 2>/dev/null)
+
+# .PHONY: release
+
+.PHONY: release-manifests
+release-manifests: $(KUSTOMIZE) $(RELEASE_DIR) ## Builds the manifests to publish with a release
+	$(KUSTOMIZE) build config/default > $(RELEASE_DIR)/infrastructure-components.yaml
+
+.PHONY: release-metadata
+release-metadata: $(RELEASE_DIR)
+	cp metadata.yaml $(RELEASE_DIR)/metadata.yaml
+
+.PHONY: release-templates
+release-templates: $(RELEASE_DIR)
+	cp templates/cluster-template* $(RELEASE_DIR)/
+
+
 ##@ Build Dependencies
 
 ## Location to install dependencies to
@@ -130,10 +167,14 @@ $(LOCALBIN):
 KUSTOMIZE ?= $(LOCALBIN)/kustomize
 CONTROLLER_GEN ?= $(LOCALBIN)/controller-gen
 ENVTEST ?= $(LOCALBIN)/setup-envtest
+ENVSUBST ?= $(LOCALBIN)/envsubst
+KUBECTL ?= $(LOCALBIN)/kubectl
 
 ## Tool Versions
 KUSTOMIZE_VERSION ?= v5.0.0
 CONTROLLER_TOOLS_VERSION ?= v0.11.3
+ENVSUBST_VER ?= v1.4.2
+KUBECTL_VER := v1.25.10
 
 KUSTOMIZE_INSTALL_SCRIPT ?= "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh"
 .PHONY: kustomize
@@ -155,3 +196,14 @@ $(CONTROLLER_GEN): $(LOCALBIN)
 envtest: $(ENVTEST) ## Download envtest-setup locally if necessary.
 $(ENVTEST): $(LOCALBIN)
 	test -s $(LOCALBIN)/setup-envtest || GOBIN=$(LOCALBIN) go install sigs.k8s.io/controller-runtime/tools/setup-envtest@latest
+
+.PHONY: envsubst
+envsubst: $(ENVSUBST)
+$(ENVSUBST): $(LOCALBIN)
+	GOBIN=$(LOCALBIN) go install github.com/a8m/envsubst/cmd/envsubst@$(ENVSUBST_VER)
+
+.PHONY: kubectl
+kubectl: $(KUBECTL)
+$(KUBECTL): $(LOCALBIN)
+	curl --retry 3 -fsL https://dl.k8s.io/release/$(KUBECTL_VER)/bin/$(GOOS)/$(GOARCH)/kubectl -o $(LOCALBIN)/kubectl
+	chmod +x $(KUBECTL)

README.md

@@ -25,49 +25,36 @@ make deploy
 
 2. Create your first workload cluster
 ```sh
-# cluster & infra cluster
-kubectl apply -f config/samples/cluster.yaml
-kubectl apply -f config/samples/infrastructure_v1beta1_proxmoxcluster.yaml
+# export env variables
+export CONTROLPLANE_HOST=X.X.X.X
+export PROXMOX_URL=X.X.X.X:8006
+export GATEWAY_ADDRESS=X.X.X.X
+export NAMESERVER_ADDRESS=X.X.X.X
+export PROXMOX_PASSWORD_BASE64=$(echo -n <password> | base64)
+export PROXMOX_USER_BASE64=$(echo -n <user@pam> | base64)
+export NODE_URL_BASE64=$(echo -n <node.ssh.url:22> | base64)
+export NODE_USER_BASE64=$(echo -n <node-ssh-user> | base64)
+export NODE_PASSWORD_BASE64=$(echo -n <node-ssh-password> | base64)
+
+make create-workload-cluster
+```
 
-# controlplane
-kubectl apply -f config/samples/controlplane.yaml
+3. Access your first workload cluster !!
 
-# machine & bootstrap & infra machine
-kubectl apply -f config/samples/machine.yaml
-kubectl apply -f config/samples/bootstrap.yaml
-kubectl apply -f config/samples/infrastructure_v1beta1_proxmoxcluster.yaml
+Usually it takes 2~5 mins to complete bootstrap the nodes.
+```sh
+# get workload cluster's kubeconfig
+clusterctl get kubeconfig cappx-test > kubeconfig.yaml
 
-# proxmox configs
-kubetl apply -f <your-proxmox-config-secret>.yaml
+# get node command for workload cluster
+kubectl --kubeconfig=kubeconfig.yaml get node
 ```
 
-You need to provide your proxmox information through secret. 
-```yaml
-# <your-proxmox-config-secret>.yaml
-apiVersion: v1
-data:
-  # for proxmox API
-  PROXMOX_PASSWORD: "<base 64>"
-  PROXMOX_USER: "<base 64>"
-  # for ssh into the node to bootstrapping VMs
-  ## * current CAPP is compatible with only single node proxmox cluster
-  NODE_URL: "<base 64>"
-  NODE_USER: "<base 64>"
-  NODE_PASSWORD: "<base 64>"
-kind: Secret
-metadata:
-  name: proxmoxcluster-sample
-type: Opaque
+4. Tear down your workload cluster
+```sh
+make delete-workload-cluster
 ```
 
-3. Check your Cluster & Machines !!
-
-Once CAPP reconciled your `ProxmoxCluster`/`ProxmoxMachine`, you can see `READY=true` for `ProxmoxCluster` and `STATUS=running` for `ProxmoxMachine`.
-
-![kubectl-get-proxmox-cluster](./logos/k-get-proxmoxcluster.PNG)
-
-![kubectl-get-proxmox-machine](./logos/k-get-proxmoxmachine.PNG)
-
 ## Fetures
 
 - No need to prepare vm templates. You can specify any vm image in `ProxmoxMachine.Spec.Image`.