update templates/README according to code changes

Author: sp-yduck

README.md

@@ -24,15 +24,10 @@ clusterctl init --infrastructure=proxmox:v0.2.3 --config https://raw.githubuserc
 2. Create your first workload cluster
 ```sh
 # export env variables
-export CONTROLPLANE_HOST=X.X.X.X                          # control-plane vip
+export CONTROLPLANE_HOST=X.X.X.X                   # control-plane vip
 export PROXMOX_URL=https://X.X.X.X:8006/api2/json
-# export PROXMOX_PASSWORD=password                        # (optional)
-# export PROXMOX_USER=user@pam                            # (optional)
-export PROXMOX_TOKENID='root@pam!api-token-id'            # (optional)
-export PROXMOX_SECRET=aaaaaaaa-bbbb-cccc-dddd-ee12345678  # (optional)
-export NODE_URL=node.ssh.url:22
-export NODE_USER=node-ssh-user
-export NODE_PASSWORD=node-ssh-password
+export PROXMOX_PASSWORD=password
+export PROXMOX_USER=user@pam
 
 # generate manifests (available flags: --target-namespace, --kubernetes-version, --control-plane-machine-count, --worker-machine-count)
 clusterctl generate cluster cappx-test --control-plane-machine-count=3 --infrastructure=proxmox:v0.2.3 --config https://raw.githubusercontent.com/sp-yduck/cluster-api-provider-proxmox/main/clusterctl.yaml > cappx-test.yaml
@@ -62,9 +57,11 @@ kubectl delete cluster cappx-test
 
 ## Fetures
 
-- No need to prepare vm templates. You can specify any vm image in `ProxmoxMachine.Spec.Image`.
+- No need to prepare vm templates. You can specify any vm image in `ProxmoxMachine.Spec.Image`. CAPPX bootstrap your vm from scratch.
 
-- Supports custom cloud-config (user data). CAPPX uses ssh for bootstrapping nodes so it can applies custom cloud-config that can not be achieved by only Proxmox API.
+- Supports qcow2 image format. CAPPX uses VNC websocket for downloading/installing node images so it can support raw image format not ISO (Proxmox API can only support ISO)
+
+- Supports custom cloud-config (user data). CAPPX uses VNC websockert for bootstrapping nodes so it can applies custom cloud-config that can not be achieved by only Proxmox API.
 
 ### Node Images
 
@@ -99,7 +96,7 @@ This project aims to follow the Cluster API [Provider contract](https://cluster-
 
 ### ProxmoxCluster
 
-Because Proxmox-VE does not provide LBaaS solution, CAPPX does not follow the [typical infra-cluster logic](https://cluster-api.sigs.k8s.io/developer/providers/cluster-infrastructure.html#behavior). ProxmoxCluster controller reconciles only Proxmox storages used for instances. You need to prepare control plane load balancer by yourself if you creates HA control plane workload cluster.
+Because Proxmox-VE does not provide LBaaS solution, CAPPX does not follow the [typical infra-cluster logic](https://cluster-api.sigs.k8s.io/developer/providers/cluster-infrastructure.html#behavior). ProxmoxCluster controller reconciles only Proxmox storages used for instances. You need to prepare control plane load balancer by yourself if you creates HA control plane workload cluster. In the [cluster-template.yaml](./templates/cluster-template.yaml), you can find HA control plane example with [kube-vip](https://github.com/kube-vip/kube-vip).
 
 ### ProxmoxMachine
 

templates/cluster-template.yaml

@@ -35,10 +35,6 @@ spec:
     endpoint: "${PROXMOX_URL}"
     secretRef:
       name: "${CLUSTER_NAME}"
-  nodeRefs:
-    - name: mynode
-      secretRef:
-        name: "${CLUSTER_NAME}"
   storage:
     name: "${CLUSTER_NAME}"
     path: ""
@@ -318,9 +314,6 @@ stringData:
   PROXMOX_USER: ${PROXMOX_USER:=""}
   PROXMOX_TOKENID: ${PROXMOX_TOKENID:=""}
   PROXMOX_SECRET: ${PROXMOX_SECRET:=""}
-  NODE_URL: ${NODE_URL}
-  NODE_USER: ${NODE_USER}
-  NODE_PASSWORD: ${NODE_PASSWORD}
 kind: Secret
 metadata:
   name: "${CLUSTER_NAME}"