# Development


## Prerequisites

To start developing K3k you will need:

- Go
- Docker
- Helm
- A running Kubernetes cluster


> [!IMPORTANT]
> 
> Virtual clusters in shared mode need to have a configured storage provider, unless the `--persistence-type ephemeral` flag is used.
> 
> To install the [`local-path-provisioner`](https://github.com/rancher/local-path-provisioner) and set it as the default storage class you can run:
> 
> ```
> kubectl apply -f https://raw.githubusercontent.com/rancher/local-path-provisioner/v0.0.34/deploy/local-path-storage.yaml
> kubectl patch storageclass local-path -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
> ```


### TLDR

```shell
#!/bin/bash

set -euo pipefail

# These environment variables configure the image repository and tag.
export REPO=ghcr.io/myuser
export VERSION=dev-$(date -u '+%Y%m%d%H%M')

make
make push
make install
```

### Makefile

To see all the available Make commands you can run `make help`, i.e:

```
-> % make help
  all                            Run 'make' or 'make all' to run 'version', 'generate', 'build' and 'package'
  version                        Print the current version
  build                          Build the the K3k binaries (k3k, k3k-kubelet and k3kcli)
  package                        Package the k3k and k3k-kubelet Docker images
  push                           Push the K3k images to the registry
  test                           Run all the tests
  test-unit                      Run the unit tests (skips the e2e)
  test-controller                Run the controller tests (pkg/controller)
  test-kubelet-controller        Run the controller tests (pkg/controller)
  test-e2e                       Run the e2e tests
  test-cli                       Run the cli tests
  generate                       Generate the CRDs specs
  docs                           Build the CRDs and CLI docs
  docs-crds                      Build the CRDs docs
  docs-cli                       Build the CLI docs
  lint                           Find any linting issues in the project
  fmt                            Format source files in the project
  validate                       Validate the project checking for any dependency or doc mismatch
  install                        Install K3k with Helm on the targeted Kubernetes cluster
  help                           Show this help.
```

### Build

To build the needed binaries (`k3k`, `k3k-kubelet` and the `k3kcli`) and package the images you can simply run `make`.

By default the `rancher` repository will be used, but you can customize this to your registry with the `REPO` env var:

```
REPO=ghcr.io/userorg make
```

To customize the tag you can also explicitly set the VERSION:

```
VERSION=dev-$(date -u '+%Y%m%d%H%M') make
```


### Push

You will need to push the built images to your registry, and you can use the `make push` command to do this.


### Install

Once you have your images available you can install K3k with the `make install` command. This will use `helm` to install the release.


## Tests

To run the tests you can just run `make test`, or one of the other available "sub-tests" targets (`test-unit`, `test-controller`, `test-e2e`, `test-cli`).

When running the tests the namespaces used are cleaned up. If you want to keep them to debug you can use the `KEEP_NAMESPACES`, i.e.:

```
KEEP_NAMESPACES=true make test-e2e
```

The e2e and cli tests run against the cluster configured in your KUBECONFIG environment variable. Running the tests with the `K3K_DOCKER_INSTALL` environment variable set will use `tescontainers` instead:

```
K3K_DOCKER_INSTALL=true make test-e2e
```


We use [Ginkgo](https://onsi.github.io/ginkgo/), and [`envtest`](https://book.kubebuilder.io/reference/envtest) for testing the controllers.

The required binaries for `envtest` are installed with [`setup-envtest`](https://pkg.go.dev/sigs.k8s.io/controller-runtime/tools/setup-envtest), in the `.envtest` folder.


## CRDs and Docs

We are using Kubebuilder and `controller-gen` to build the needed CRDs. To generate the specs you can run `make generate`.

Remember also to update the CRDs documentation running the `make docs` command.

## How to install k3k on k3d

This document provides a guide on how to install k3k on [k3d](https://k3d.io).

### Installing k3d

Since k3d uses docker under the hood, we need to expose the ports on the host that we'll then use for the NodePort in virtual cluster creation.

Create the k3d cluster in the following way:

```bash
k3d cluster create k3k -p "30000-30010:30000-30010@server:0"
```

With this syntax ports from 30000 to 30010 will be exposed on the host.

### Install k3k

Install now k3k as usual:

```bash
helm repo update
helm install --namespace k3k-system --create-namespace k3k k3k/k3k
```

### Create a virtual cluster

Once the k3k controller is up and running, create a namespace where to create our first virtual cluster.

```bash
kubectl create ns k3k-mycluster
```

Create then the virtual cluster exposing through NodePort one of the ports that we set up in the previous step:

```bash
cat <<EOF | kubectl apply -f -
apiVersion: k3k.io/v1beta1
kind: Cluster
metadata:
  name: mycluster
  namespace: k3k-mycluster
spec:    
  expose:
    nodePort:
      serverPort: 30001
EOF
```

Check when the cluster is ready:

```bash
kubectl get po -n k3k-mycluster
```

Last thing to do is to get the kubeconfig to connect to the virtual cluster we've just created:

```bash
k3kcli kubeconfig generate --name mycluster --namespace k3k-mycluster --kubeconfig-server localhost:30001
```


> [!IMPORTANT]
> Because of technical limitation is not possible to create virtual clusters in `virtual` mode with K3d, or any other dockerized environment (Kind, Minikube)