Spin Operator enables deploying Spin applications to Kubernetes. It watches SpinApp Custom Resources and realizes the desired state in the Kubernetes cluster.

This project was built using the Kubebuilder framework and contains a Spin App CRD and controller.

All documentation is available online at https://www.spinkube.dev/docs/. If you're just getting started, the quickstart guide will guide you to a minimal installation that'll work while you walk through the introduction.

To get more help:

• Join the #spinkube channel on Slack at https://cncf.slack.com.

To contribute to SpinKube, check out the contributing guide for information about getting involved.

To run the test suite, execute the following command:

make test

To build the Spin Operator binary, execute the following command:

make

There are two options to run spin-operator:

1. Run spin-operator on your computer
2. Deploy spin-operator to a remote Kubernetes cluster

k3d is a lightweight Kubernetes distribution that runs on Docker. This is the standard development workflow most spin-operator developers use to test their changes.

Ensure that your system has all the prerequisites installed before continuing:

• Go
• Docker
• k3d
• kubectl

Create a k3d cluster:

k3d cluster create wasm-cluster \
    --image ghcr.io/spinkube/containerd-shim-spin/k3d:v0.15.1 \
    -p "8081:80@loadbalancer" \
    --agents 2

Install the SpinApp and SpinAppExecutor Custom Resource Definitions into the cluster:

make install

Create a RuntimeClass and SpinAppExecutor:

kubectl apply -f config/samples/spin-runtime-class.yaml
kubectl apply -f config/samples/spin-shim-executor.yaml

Run spin-operator:

make run

Run the sample application:

kubectl apply -f ./config/samples/simple.yaml

Forward a local port to the application so that it can be reached:

kubectl port-forward svc/simple-spinapp 8083:80

In a different terminal window, make a request to the application:

curl localhost:8083/hello

You should see "Hello world from Spin!".

This is harder than running Spin Operator on your computer, but deploying Spin Operator into a remote cluster lets you test things like webhook support.

Ensure that your system has all the prerequisites installed before continuing:

• Go
• kubectl
• Docker (optional: for building and pushing your own Docker image)

Install cert-manager into your cluster for webhook support:

kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.3/cert-manager.yaml
kubectl wait --for=condition=available --timeout=300s deployment/cert-manager-webhook -n cert-manager

Install the SpinApp and SpinAppExecutor Custom Resource Definitions into the cluster:

make install

Create a RuntimeClass and SpinAppExecutor:

kubectl apply -f config/samples/spin-runtime-class.yaml
kubectl apply -f config/samples/spin-shim-executor.yaml

OPTIONAL: You can build and push the Spin Operator image using make docker-build and make docker-push.

export IMG_REPO=<some-registry>/spin-operator
make docker-build docker-push

Deploy Spin Operator to the cluster:

make deploy

Run the sample application:

kubectl apply -f ./config/samples/simple.yaml

Forward a local port to the application so that it can be reached:

kubectl port-forward svc/simple-spinapp 8083:80

In a different terminal window, make a request to the application:

curl localhost:8083/hello

You should see "Hello world from Spin!".

NOTE: If you encounter RBAC errors, you may need to grant yourself cluster-admin privileges or be logged in as admin.