A Kubernetes Operator to instanciate and control headscale instances
Go to file
2023-09-28 08:55:08 +02:00
api/v1alpha1 Initial Commit 🎉 2022-06-23 16:15:33 +02:00
config Initial Commit 🎉 2022-06-23 16:15:33 +02:00
controllers Initial Commit 🎉 2022-06-23 16:15:33 +02:00
hack Initial Commit 🎉 2022-06-23 16:15:33 +02:00
pkg Initial Commit 🎉 2022-06-23 16:15:33 +02:00
.dockerignore Initial Commit 🎉 2022-06-23 16:15:33 +02:00
.gitignore Initial Commit 🎉 2022-06-23 16:15:33 +02:00
Dockerfile Initial Commit 🎉 2022-06-23 16:15:33 +02:00
go.mod Initial Commit 🎉 2022-06-23 16:15:33 +02:00
go.sum Initial Commit 🎉 2022-06-23 16:15:33 +02:00
LICENSE Initial Commit 🎉 2022-06-23 16:15:33 +02:00
main.go Initial Commit 🎉 2022-06-23 16:15:33 +02:00
Makefile Initial Commit 🎉 2022-06-23 16:15:33 +02:00
PROJECT Initial Commit 🎉 2022-06-23 16:15:33 +02:00
README.md Add missing install step to README.md 2023-09-28 08:55:08 +02:00

headscale-operator

A Kubernetes Operator to instantiate and control headscale instances.

Description

With headscale-operator you can instantiate multiple headscale servers for multiple purpose.

headscale-operator let you manage namespaces and preauthkeys.

Getting Started

Youll need a Kubernetes cluster to run against. You can use KIND to get a local cluster for testing, or run against a remote cluster. Note: Your controller will automatically use the current context in your kubeconfig file (i.e. whatever cluster kubectl cluster-info shows).

Running on the cluster

  1. Install Instances of Custom Resources:
kubectl apply -f config/crd/bases/
kubectl apply -f config/samples/
  1. Build and push your image to the location specified by IMG:
make docker-build docker-push IMG=<some-registry>/headscale-operator:tag
  1. Deploy the controller to the cluster with the image specified by IMG:
make deploy IMG=<some-registry>/headscale-operator:tag

Uninstall CRDs

To delete the CRDs from the cluster:

make uninstall

Undeploy controller

UnDeploy the controller to the cluster:

make undeploy

How it works

This project aims to follow the Kubernetes Operator pattern

It uses Controllers which provides a reconcile function responsible for synchronizing resources untile the desired state is reached on the cluster

Test It Out

  1. Install the CRDs into the cluster:
make install
  1. Run your controller (this will run in the foreground, so switch to a new terminal if you want to leave it running):
make run

NOTE: You can also run this in one step by running: make install run

Modifying the API definitions

If you are editing the API definitions, generate the manifests such as CRs or CRDs using:

make manifests

NOTE: Run make --help for more information on all potential make targets

More information can be found via the Kubebuilder Documentation

License

Copyright 2022 Guilhem Lettron.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.