K3d single instance

Use case development

Run pre-flight checks with:

infctl-preflight-checks --set 0
infctl-preflight-checks

If this command is missing, install infctl.

You need to see the following before proceeding.

Results:
  Tools checked: 1
  Found: 1
  Missing: 0

  ✓ docker - Docker version 29.0.2, build 8108357

If docker is not present, install it - see Pre Requisites.

Next, start your development environment

and take a look at the script ./infra/k3d/scripts/create_k3d_cluster.sh

familiarize yourself with what it does and when ready to run it

./infra/k3d/scripts/create_k3d_cluster.sh

k3d can also list this and any other clusters you have running locally with

k3d cluster list
NAME        SERVERS   AGENTS   LOADBALANCER
mycluster   1/1       0/0      true

if all goes well, you should have a k3d ( k3s ) cluster running locally that you can see its single node running with

kubectl get nodes
NAME                     STATUS   ROLES                  AGE   VERSION
k3d-mycluster-server-0   Ready    control-plane,master   93m   v1.31.5+k3s1

A healthy state and most of the resources may be viewed in several ways but 2 for starters can be:

kubectl get events -A
kubectl get all -A

The first will list any events logged by the cluster.

The second will list ‘all’ resources which can be a bit misleading as not all the things are actually listed, just the main ones we are interested in.

When your done with this secion and are ready to, delete the cluster ( you can create a new one any time with the above command )

k3d cluster delete mycluster