2024-12-13 09:09:14 +01:00
# Image URL to use all building/pushing image targets
IMG ?= controller:latest
# ENVTEST_K8S_VERSION refers to the version of kubebuilder assets to be downloaded by envtest binary.
ENVTEST_K8S_VERSION = 1.31.0
# Get the currently used golang install path (in GOPATH/bin, unless GOBIN is set)
i f e q ( , $( shell go env GOBIN ) )
GOBIN = $( shell go env GOPATH) /bin
e l s e
GOBIN = $( shell go env GOBIN)
e n d i f
# CONTAINER_TOOL defines the container tool to be used for building images.
# Be aware that the target commands are only tested with Docker which is
# scaffolded by default. However, you might want to replace it to use other
# tools. (i.e. podman)
CONTAINER_TOOL ?= docker
# Setting SHELL to bash allows bash commands to be executed by recipes.
# Options are set to exit when a recipe line exits non-zero or a piped command fails.
SHELL = /usr/bin/env bash -o pipefail
.SHELLFLAGS = -ec
.PHONY : all
all : build
##@ General
# The help target prints out all targets with their descriptions organized
# beneath their categories. The categories are represented by '##@' and the
# target descriptions by '##'. The awk command is responsible for reading the
# entire set of makefiles included in this invocation, looking for lines of the
# file as xyz: ## something, and then pretty-format the target and help. Then,
# if there's a line with ##@ something, that gets pretty-printed as a category.
# More info on the usage of ANSI control characters for terminal formatting:
# https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_parameters
# More info on the awk command:
# http://linuxcommand.org/lc3_adv_awk.php
.PHONY : help
help : ## Display this help.
@awk 'BEGIN {FS = ":.*##"; printf "\nUsage:\n make \033[36m<target>\033[0m\n"} /^[a-zA-Z_0-9-]+:.*?##/ { printf " \033[36m%-15s\033[0m %s\n", $$1, $$2 } /^##@/ { printf "\n\033[1m%s\033[0m\n", substr($$0, 5) } ' $( MAKEFILE_LIST)
##@ Development
.PHONY : manifests
2025-02-13 19:48:45 +01:00
manifests : ## Generate WebhookConfiguration, ClusterRole and CustomResourceDefinition objects.
2024-12-13 09:09:14 +01:00
$( CONTROLLER_GEN) rbac:roleName= manager-role crd webhook paths = "./..." output:crd:artifacts:config= config/crd/bases
.PHONY : generate
2025-02-13 19:48:45 +01:00
generate : ## Generate code containing DeepCopy, DeepCopyInto, and DeepCopyObject method implementations.
2024-12-13 09:09:14 +01:00
$( CONTROLLER_GEN) object:headerFile= "hack/boilerplate.go.txt" paths = "./..."
.PHONY : fmt
fmt : ## Run go fmt against code.
go fmt ./...
.PHONY : vet
vet : ## Run go vet against code.
go vet ./...
.PHONY : test
2025-02-13 19:48:45 +01:00
test : manifests generate fmt vet ## Run tests.
2024-12-13 09:09:14 +01:00
KUBEBUILDER_ASSETS = " $( shell $( ENVTEST) use $( ENVTEST_K8S_VERSION) --bin-dir $( LOCALBIN) -p path) " go test $$ ( go list ./... | grep -v /e2e) -coverprofile cover.out
# TODO(user): To use a different vendor for e2e tests, modify the setup under 'tests/e2e'.
# The default setup assumes Kind is pre-installed and builds/loads the Manager Docker image locally.
# Prometheus and CertManager are installed by default; skip with:
# - PROMETHEUS_INSTALL_SKIP=true
# - CERT_MANAGER_INSTALL_SKIP=true
.PHONY : test -e 2e
test-e2e : manifests generate fmt vet ## Run the e2e tests. Expected an isolated environment using Kind.
@command -v kind >/dev/null 2>& 1 || { \
echo "Kind is not installed. Please install Kind manually." ; \
exit 1; \
}
@kind get clusters | grep -q 'kind' || { \
echo "No Kind cluster is running. Please start a Kind cluster before running the e2e tests." ; \
exit 1; \
}
go test ./test/e2e/ -v -ginkgo.v
.PHONY : lint
2025-02-13 19:48:45 +01:00
lint : ## Run golangci-lint linter
2024-12-13 09:09:14 +01:00
$( GOLANGCI_LINT) run
.PHONY : lint -fix
2025-02-13 19:48:45 +01:00
lint-fix : ## Run golangci-lint linter and perform fixes
2024-12-13 09:09:14 +01:00
$( GOLANGCI_LINT) run --fix
##@ Build
.PHONY : build
build : manifests generate fmt vet ## Build manager binary.
go build -o bin/manager cmd/main.go
.PHONY : run
run : manifests generate fmt vet ## Run a controller from your host.
go run ./cmd/main.go
# If you wish to build the manager image targeting other platforms you can use the --platform flag.
# (i.e. docker build --platform linux/arm64). However, you must enable docker buildKit for it.
# More info: https://docs.docker.com/develop/develop-images/build_enhancements/
.PHONY : docker -build
docker-build : ## Build docker image with the manager.
$( CONTAINER_TOOL) build -t ${ IMG } .
.PHONY : docker -push
docker-push : ## Push docker image with the manager.
$( CONTAINER_TOOL) push ${ IMG }
# PLATFORMS defines the target platforms for the manager image be built to provide support to multiple
# architectures. (i.e. make docker-buildx IMG=myregistry/mypoperator:0.0.1). To use this option you need to:
# - be able to use docker buildx. More info: https://docs.docker.com/build/buildx/
# - have enabled BuildKit. More info: https://docs.docker.com/develop/develop-images/build_enhancements/
# - be able to push the image to your registry (i.e. if you do not set a valid value via IMG=<myregistry/image:<tag>> then the export will fail)
# To adequately provide solutions that are compatible with multiple platforms, you should consider using this option.
PLATFORMS ?= linux/arm64,linux/amd64,linux/s390x,linux/ppc64le
.PHONY : docker -buildx
docker-buildx : ## Build and push docker image for the manager for cross-platform support
# copy existing Dockerfile and insert --platform=${BUILDPLATFORM} into Dockerfile.cross, and preserve the original Dockerfile
sed -e '1 s/\(^FROM\)/FROM --platform=\$$\{BUILDPLATFORM\}/; t' -e ' 1,// s//FROM --platform=\$$\{BUILDPLATFORM\}/' Dockerfile > Dockerfile.cross
- $( CONTAINER_TOOL) buildx create --name supabase-operator-builder
$( CONTAINER_TOOL) buildx use supabase-operator-builder
- $( CONTAINER_TOOL) buildx build --push --platform= $( PLATFORMS) --tag ${ IMG } -f Dockerfile.cross .
- $( CONTAINER_TOOL) buildx rm supabase-operator-builder
rm Dockerfile.cross
.PHONY : build -installer
2025-02-13 19:48:45 +01:00
build-installer : manifests generate ## Generate a consolidated YAML with CRDs and deployment.
2024-12-13 09:09:14 +01:00
mkdir -p dist
cd config/manager && $( KUSTOMIZE) edit set image controller = ${ IMG }
$( KUSTOMIZE) build config/default > dist/install.yaml
##@ Deployment
i f n d e f i g n o r e - n o t - f o u n d
ignore-not-found = false
e n d i f
.PHONY : install
install : manifests kustomize ## Install CRDs into the K8s cluster specified in ~/.kube/config.
$( KUSTOMIZE) build config/crd | $( KUBECTL) apply -f -
.PHONY : uninstall
uninstall : manifests kustomize ## Uninstall CRDs from the K8s cluster specified in ~/.kube/config. Call with ignore-not-found=true to ignore resource not found errors during deletion.
$( KUSTOMIZE) build config/crd | $( KUBECTL) delete --ignore-not-found= $( ignore-not-found) -f -
.PHONY : deploy
deploy : manifests kustomize ## Deploy controller to the K8s cluster specified in ~/.kube/config.
2025-02-13 09:29:47 +01:00
cd config/manager && $( KUSTOMIZE) edit set image supabase-operator= ${ IMG }
2024-12-13 09:09:14 +01:00
$( KUSTOMIZE) build config/default | $( KUBECTL) apply -f -
.PHONY : undeploy
undeploy : kustomize ## Undeploy controller from the K8s cluster specified in ~/.kube/config. Call with ignore-not-found=true to ignore resource not found errors during deletion.
$( KUSTOMIZE) build config/default | $( KUBECTL) delete --ignore-not-found= $( ignore-not-found) -f -
##@ Dependencies
## Location to install dependencies to
LOCALBIN ?= $( shell pwd ) /bin
$(LOCALBIN) :
mkdir -p $( LOCALBIN)
## Tool Binaries
KUBECTL ?= kubectl
2025-02-13 19:48:45 +01:00
KUSTOMIZE ?= go tool kustomize
CONTROLLER_GEN ?= go tool controller-gen
ENVTEST ?= go tool setup-envtest
GOLANGCI_LINT = go tool golangci-lint