Skip to content

Permanent CAPI management cluster and workload cluster applied by FluxCD
Compare
Choose a tag to compare
@olga-mir olga-mir released this 29 May 04:08
· 219 commits to main since this release
0.0.1
414599c
This commit was signed with the committer’s verified signature. The key has expired.
olga-mir Olga Mirensky
GPG key ID: 7F62728098EFD5DE
Expired
Learn about vigilant mode.

First iteration of CAPI + FluxCD.
./scripts/deploy-bootstrap-cluster.sh - implements bootstrap and pivot approach as described here: https://cluster-api.sigs.k8s.io/clusterctl/commands/move.html#bootstrap--pivot except that temporary management cluster is not deleted. This is because without it currently it is not clear how to manage the permanent management cluster.
Following that, running scripts/install-flux.sh installs FluxCD on permanent management cluster and applies config which includes workload cluster definition.

% k config use-context mgmt-admin@mgmt 
Switched to context "mgmt-admin@mgmt".
% k get nodes 
NAME                                              STATUS   ROLES                  AGE     VERSION
ip-10-0-222-144.ap-southeast-2.compute.internal   Ready    <none>                 3m50s   v1.22.8
ip-10-0-230-230.ap-southeast-2.compute.internal   Ready    control-plane,master   4m51s   v1.22.8

connect to dev cluster:

% clusterctl get kubeconfig dev -n cluster-dev > dev.kubeconfig 
% k get nodes --kubeconfig=./dev.kubeconfig --context dev-admin@dev
NAME                                             STATUS     ROLES                  AGE     VERSION
ip-10-0-196-17.ap-southeast-2.compute.internal   NotReady   <none>                 108s    v1.21.11
ip-10-0-231-67.ap-southeast-2.compute.internal   NotReady   control-plane,master   2m43s   v1.21.11

(still needs CNI to properly finish the install)

Assets 2
Loading