Merge pull request #14 from SovereignCloudStack/feat/implement-wait

Feat/implement wait

Author: garloff

01-kind-cluster.sh

@@ -17,3 +17,4 @@ if test "$(kind get clusters)" != "kind"; then
 else
 	echo "kind cluster already running"
 fi
+kubectl cluster-info

03-deploy-cso.sh

@@ -26,3 +26,4 @@ EOF
 helm upgrade -i cso -n cso-system \
 	--create-namespace --values ~/tmp/cso-rbac.yaml \
 	oci://registry.scs.community/cluster-stacks/cso
+kubectl -n cso-system rollout status deployment

06-wait-clusterclass.sh

@@ -12,10 +12,7 @@ else
 fi
 # Read settings -- make sure you can trust it
 source "$SET"
-# ToDo: Wait for cluster class
-echo "The clusterclass should exist now"
-echo "WARN: Waiting not yet implemented"
-sleep 3
-set -x
-kubectl get images -n "$CS_NAMESPACE"
+kubectl wait -n "$CS_NAMESPACE" clusterclass openstack-scs-${CS_MAINVER/./-}-${CS_VERSION} --for create
 kubectl get clusterclasses -n "$CS_NAMESPACE"
+kubectl get images -n "$CS_NAMESPACE"
+kubectl wait -n "$CS_NAMESPACE" clusterstackrelease openstack-scs-${CS_MAINVER/./-}-${CS_VERSION/./-} --for condition=ready

08-wait-cluster.sh

@@ -11,9 +11,13 @@ else
 fi
 # Read settings -- make sure you can trust it
 source "$SET"
-# ToDo: Wait for cluster
-echo "The cluster should exist now"
-echo "WARN: Waiting not yet implemented"
-set -x
-clusterctl describe cluster -n "$CS_NAMESPACE" $CL_NAME
-echo "clusterctl get kubeconfig -n $CS_NAMESPACE $CL_NAME > ~/.kube/config-$CS_NAMESPACE.$CL_NAME"
+kubectl get cluster -A
+#set -x
+kubectl wait --timeout=14m --for=condition=certificatesavailable -n "$CS_NAMESPACE" kubeadmcontrolplanes -l cluster.x-k8s.io/cluster-name=$CL_NAME
+kubectl get -n "$CS_NAMESPACE" cluster $CL_NAME
+clusterctl describe cluster -n "$CS_NAMESPACE" $CL_NAME --grouping=false
+KCFG=~/.kube/$CS_NAMESPACE.$CL_NAME
+clusterctl get kubeconfig -n "$CS_NAMESPACE" $CL_NAME > $KCFG
+KUBECONFIG=$KCFG kubectl get nodes -o wide
+KUBECONFIG=$KCFG kubectl get pods -A
+echo "# Hint: Use KUBECONFIG=$KCFG kubectl ... to access you workload cluster $CS_NAMESPACE/$CL_NAME"

16-cleanup-cluster.sh

@@ -0,0 +1,6 @@
+#!/bin/bash
+set -e
+# Create 16-cleanup-cluster.sh script
+echo "Cleaning cluster not yet implemented."
+echo "Hint: Please delete Loadbalancers and persistent volumes before deleting cluster."
+

18-delete-kind.sh

@@ -0,0 +1,4 @@
+#!/bin/bash
+set -e
+kind delete cluster
+docker network rm kind

README.md

@@ -25,6 +25,8 @@ copy, fill it in, and pass it to the scripts.
 * 02-deploy-capi.sh: Install ORC and CAPI.
 * 03-deploy-cso.sh: Install the Cluster Stack Operator.
 
+* 18-delete-kind.sh: Remove kind cluster management again.
+
 ### Once per OpenStack Project in which we want to install clusters (NS)
 * 04-cloud-secret.sh: Create namespace and secrets to work with the
   wanted OpenStack project.
@@ -33,13 +35,14 @@ copy, fill it in, and pass it to the scripts.
 * 05-deploy-cstack.sh: Create the Cluster Stack which is a template
   for various clusters with the same major minor version of k8s.
   Should trigger cluster class creation and image registration.
-* 06-wait-clusterclass.sh: Wait for the cluster class (not yet implemented)
+* 06-wait-clusterclass.sh: Wait for the cluster class
 
 ### Once per cluster
 * 07-create-cluster.sh: Create a workload cluster as per all the settings
   that are passed.
-* 08-wait-cluster.sh: Wait for the workload cluster (not yet implemented)
+* 08-wait-cluster.sh: Wait for the workload cluster
 
+* 16-cleanup-cluster.sh: Remove loadbalancers and persistent volumes from cluster.
 * 17-delete-cluster.sh: Remove cluster again.
 
 ### CSI Cinder fixup
@@ -53,3 +56,12 @@ to a non-existing file, see [ClusterStacks issue #188](https://github.com/Sovere
 This results in a `CrashLoopBackup` state for
 the openstack-cinder-csi-* pods in the workload cluster. Until this
 is fixed up upstream, it can be patched using the `09-fixup-cinder.sh`.
+
+### Moving management to a new cluster
+The bootstrap KinD management cluster (host) is not set up in a way
+that is robust enough for long-term operation. So we should move the
+CAPI, CAPO, CSO management objects into a more resilient k8s cluster,
+as is supported with `clusterctl move`. Beyond the capi, capi resources,
+this requires tracking all other management resources (objects from
+ORC, CSO etc.) -- once this is complete, a script will be offered
+to facilitate this.