docs: adopt latest changes

Author: vknabel

DEVELOPMENT.md

@@ -18,13 +18,13 @@ Next install our CAPMS provider into the cluster.
 make push-to-capi-lab
 ```
 
-Before creating a cluster some manual steps are required beforehand: you need to allocate a node network.
+Before creating a cluster the control plane IP needs to be created first:
 
 ```bash
-make -C capi-lab node-network control-plane-ip
+make -C capi-lab control-plane-ip
 ```
 
-A basic cluster configuration that relies on `config/clusterctl-templates/cluster-template.yaml` and uses the aforementioned node network can be generated and applied to the management cluster using a make target.
+A basic cluster configuration that relies on `config/clusterctl-templates/cluster-template-calico.yaml` and uses the aforementioned IP can be generated and applied to the management cluster using a make target.
 
 ```bash
 make -C capi-lab apply-sample-cluster
@@ -159,7 +159,6 @@ export METAL_API_URL=
 
 export METAL_PARTITION=
 export METAL_PROJECT_ID=
-export METAL_NODE_NETWORK_ID=
 export CONTROL_PLANE_IP=
 
 export FIREWALL_MACHINE_IMAGE=
@@ -183,11 +182,10 @@ export project_name=
 export tenant_name=
 ```
 
-Create project, node network and control plane ip if needed:
+Create project and control plane ip if needed:
 
 ```bash
 metalctl project create --name $project_name --tenant $tenant_name --description "Cluster API test project"
-metalctl network allocate --description "Node network for $CLUSTER_NAME" --name $CLUSTER_NAME --project $METAL_PROJECT_ID --partition $METAL_PARTITION
 metalctl network ip create --network internet --project $METAL_PROJECT_ID --name "$CLUSTER_NAME-vip" --type static -o template --template "{{ .ipaddress }}"
 ```
 

README.md

@@ -14,7 +14,6 @@ Currently, we provide the following custom resources:
 
 We plan to cover more resources in the future:
 
-- Node Networks
 - Complete Firewall Deployments using the [Firewall Controller Manager](https://github.com/metal-stack/firewall-controller-manager)
 - Improved configuration suggestion of CNIs
 
@@ -59,28 +58,21 @@ clusterctl init --infrastructure metal-stack
 > **Manual steps needed:**
 > Due to the early development stage, manual actions are needed for the cluster to operate. Some metal-stack resources need to be created manually.
 
-A node network needs to be created.
+Allocate a VIP for the control plane.
+
 ```bash
 export CLUSTER_NAME=<cluster-name>
 export METAL_PARTITION=<partition>
 export METAL_PROJECT_ID=<project-id>
-metalctl network allocate --description "Node network for $CLUSTER_NAME" --name $CLUSTER_NAME --project $METAL_PROJECT_ID --partition $METAL_PARTITION
 
-# export environment variable for use in the next steps
-export METAL_NODE_NETWORK_ID=$(metalctl network list --name $CLUSTER_NAME -o template --template '{{ .id }}')
-```
-
-Allocate a VIP for the control plane.
-
-```bash
 export CONTROL_PLANE_IP=$(metalctl network ip create --network internet --project $METAL_PROJECT_ID --name "$CLUSTER_NAME-vip" --type static -o template --template "{{ .ipaddress }}")
 ```
 
 For your first cluster, it is advised to start with our generated template. Ensure that the namespaced cluster name is unique within the metal stack project.
 
 ```bash
 # display required environment variables
-clusterctl generate cluster $CLUSTER_NAME --infrastructure metal-stack --list-variables
+clusterctl generate cluster $CLUSTER_NAME --infrastructure metal-stack --list-variables --flavor calico
 
 # set additional environment variables
 export CONTROL_PLANE_MACHINE_IMAGE=<machine-image>
@@ -91,7 +83,7 @@ export FIREWALL_MACHINE_IMAGE=<machine-image>
 export FIREWALL_MACHINE_SIZE=<machine-size>
 
 # generate manifest
-clusterctl generate cluster $CLUSTER_NAME --kubernetes-version v1.32.9 --infrastructure metal-stack
+clusterctl generate cluster $CLUSTER_NAME --kubernetes-version v1.32.9 --infrastructure metal-stack --flavor calico
 ```
 
 Apply the generated manifest from the `clusterctl` output.
@@ -100,51 +92,7 @@ Apply the generated manifest from the `clusterctl` output.
 kubectl apply -f <manifest>
 ```
 
-Once your control plane and worker machines have been provisioned, you need to install your CNI of choice into your created cluster. This is required due to CAPI. An example is provided below:
-
-```bash
-# get the kubeconfig
-clusterctl get kubeconfig metal-test > capms-cluster.kubeconfig
-
-# install the calico operator
-kubectl --kubeconfig=capms-cluster.kubeconfig create -f https://raw.githubusercontent.com/projectcalico/calico/v3.28.2/manifests/tigera-operator.yaml
-
-# install the calico CNI
-cat <<EOF | kubectl --kubeconfig=capms-cluster.kubeconfig create -f -
-apiVersion: operator.tigera.io/v1
-kind: Installation
-metadata:
-  name: default
-spec:
-  # Configures Calico networking.
-  calicoNetwork:
-    bgp: Disabled
-    ipPools:
-    - name: default-ipv4-ippool
-      blockSize: 26
-      cidr: 10.240.0.0/12
-      encapsulation: None
-    mtu: 1440
-  cni:
-    ipam:
-      type: HostLocal
-    type: Calico
-EOF
-```
-
-Meanwhile, the `metal-ccm` has to be deployed for the machines to reach `Running` phase. For this use the [`config/target-cluster/metal-ccm.yaml` template](config/target-cluster/metal-ccm.yaml) and fill in the required variables.
-
-```bash
-export NAMESPACE=<namespace>
-export CLUSTER_NAME=<cluster name>
-cat config/target-cluster/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
-kubectl --kubeconfig capms-cluster.kubeconfig apply --kustomize capi-lab/metallb
-```
+That's it!
 
 ## Frequently Asked Questions
 

capi-lab/Makefile

@@ -59,17 +59,12 @@ controller:
 	kubectl --kubeconfig=$(KUBECONFIG) patch deployments.apps -n cap-metal-stack metal-stack-controller-manager --patch='{"spec":{"template":{"spec":{"containers":[{"name": "manager","imagePullPolicy":"IfNotPresent","image":"$(IMG)"}]}}}}'
 	kubectl --kubeconfig=$(KUBECONFIG) delete pod -n cap-metal-stack -l control-plane=metal-stack-controller-manager
 
-.PHONY: node-network
-node-network:
-	metalctl network allocate --description "node network for $(CLUSTER_NAME) cluster" --name $(CLUSTER_NAME) --project 00000000-0000-0000-0000-000000000001 --partition mini-lab
-
 .PHONY: control-plane-ip
 control-plane-ip:
 	metalctl network ip create --network internet-mini-lab --project $(METAL_PROJECT_ID) --name "$(CLUSTER_NAME)-vip" --type static -o template --template "{{ .ipaddress }}"
 
 .PHONY: apply-sample-cluster
 apply-sample-cluster:
-	$(eval METAL_NODE_NETWORK_ID = $(shell metalctl network list --name $(CLUSTER_NAME) -o template --template '{{ .id }}'))
 	$(eval CONTROL_PLANE_IP = $(shell metalctl network ip list --name "$(CLUSTER_NAME)-vip" -o template --template '{{ .ipaddress }}'))
 	echo  $(CLUSTER_NAME)
 	clusterctl generate cluster $(CLUSTER_NAME) \
@@ -82,7 +77,6 @@ apply-sample-cluster:
 
 .PHONY: delete-sample-cluster
 delete-sample-cluster:
-	$(eval METAL_NODE_NETWORK_ID = $(shell metalctl network list --name $(CLUSTER_NAME) -o template --template '{{ .id }}'))
 	$(eval CONTROL_PLANE_IP = $(shell metalctl network ip list --name "$(CLUSTER_NAME)-vip" -o template --template '{{ .ipaddress }}'))
 	clusterctl generate cluster $(CLUSTER_NAME) \
 		--kubeconfig=$(KUBECONFIG) \