@@ -44,40 +44,8 @@ kubectl get secret metal-test-kubeconfig -o jsonpath='{.data.value}' | base64 -d
4444clusterctl get kubeconfig metal-test > capi-lab/.capms-cluster-kubeconfig.yaml
4545```
4646
47- It is now expected to deploy a CNI to the cluster:
48-
49- ``` bash
50- kubectl --kubeconfig=capi-lab/.capms-cluster-kubeconfig.yaml create -f https://raw.githubusercontent.com/projectcalico/calico/v3.28.2/manifests/tigera-operator.yaml
51- cat << EOF | kubectl --kubeconfig=capi-lab/.capms-cluster-kubeconfig.yaml create -f -
52- apiVersion: operator.tigera.io/v1
53- kind: Installation
54- metadata:
55- name: default
56- spec:
57- # Configures Calico networking.
58- calicoNetwork:
59- bgp: Disabled
60- ipPools:
61- - name: default-ipv4-ippool
62- blockSize: 26
63- cidr: 10.240.0.0/12
64- encapsulation: None
65- mtu: 1440
66- cni:
67- ipam:
68- type: HostLocal
69- type: Calico
70- EOF
71- ```
72-
73- > [ !note]
74- > Actually, Calico should be configured using BGP (no overlay), eBPF and DSR. An example will be proposed in this repository at a later point in time.
75-
7647The node's provider ID is provided by the [ metal-ccm] ( https://github.com/metal-stack/metal-ccm ) , which needs to be deployed into the cluster:
7748
78- ``` bash
79- make -C capi-lab deploy-metal-ccm
80- ```
8149
8250If you want to provide service's of type load balancer through MetalLB by the metal-ccm, you need to deploy MetalLB:
8351
@@ -244,7 +212,7 @@ export control_plane_machine_id=
244212metalctl machine console --ipmi $control_plane_machine_id
245213# ip r
246214# sudo systemctl restart kubeadm
247- # crictl ps
215+ # crictl ps
248216# ~.
249217
250218clusterctl get kubeconfig > capms-cluster.kubeconfig
@@ -279,12 +247,15 @@ watch kubectl -n $NAMESPACE --kubeconfig kind-bootstrap.kubeconfig get cluster,m
279247# until everything is ready
280248```
281249
250+ > [ !note]
251+ > Actually, Calico should be configured using BGP (no overlay), eBPF and DSR. An example will be proposed in this repository at a later point in time.
252+
282253Now you are able to move the cluster resources as you wish:
283254
284255``` bash
285256clusterctl init --infrastructure metal-stack --kubeconfig capms-cluster.kubeconfig
286257
287- clusterctl move -n $NAMESPACE --kubeconfig kind-bootstrap.kubeconfig --to-kubeconfig capms-cluster.kubeconfig
258+ clusterctl move -n $NAMESPACE --kubeconfig kind-bootstrap.kubeconfig --to-kubeconfig capms-cluster.kubeconfig
288259# everything as expected
289260kubectl --kubeconfig -n $NAMESPACE kind-bootstrap.kubeconfig get cluster,metalstackcluster,machine,metalstackmachine,kubeadmcontrolplanes,kubeadmconfigs
290261kubectl --kubeconfig -n $NAMESPACE capms-cluster.kubeconfig get cluster,metalstackcluster,machine,metalstackmachine,kubeadmcontrolplanes,kubeadmconfigs
0 commit comments