Delegate Gitea operations to forge
This commit is contained in:
33
Makefile
33
Makefile
@@ -3,10 +3,7 @@ SHELL := /usr/bin/env bash
|
||||
|
||||
GITEA_RELEASE ?= gitea
|
||||
GITEA_NAMESPACE ?= default
|
||||
GITEA_CHART ?= gitea-charts/gitea
|
||||
GITEA_VALUES ?= helm/gitea-values.sops.yaml
|
||||
GITEA_REGISTRY_VALUES ?= helm/gitea-registry-values.yaml
|
||||
GITEA_INGRESS ?= manifests/gitea-ingress.yaml
|
||||
FORGE_REPO ?= /home/worsch/railiance-forge
|
||||
|
||||
VERGABE_RELEASE ?= vergabe-teilnahme
|
||||
VERGABE_NAMESPACE ?= vergabe-teilnahme
|
||||
@@ -21,7 +18,7 @@ VERGABE_DB_HOST ?= apps-pg-rw.databases
|
||||
VERGABE_DB_PORT ?= 5432
|
||||
VERGABE_DB_NAME ?= vergabe_db
|
||||
|
||||
SOPS_SENTINEL ?= $(GITEA_VALUES)
|
||||
SOPS_SENTINEL ?= $(FORGE_REPO)/helm/gitea-values.sops.yaml
|
||||
DRY_RUN_CREATE_NAMESPACES ?= false
|
||||
|
||||
##@ Operator checks
|
||||
@@ -35,28 +32,16 @@ check-sops: ## Verify the local SOPS age key can decrypt the configured sentinel
|
||||
k8s-server-dry-run: ## Server-side dry-run rendered Helm and committed manifests
|
||||
DRY_RUN_CREATE_NAMESPACES=$(DRY_RUN_CREATE_NAMESPACES) tools/k8s-server-dry-run.sh
|
||||
|
||||
##@ Gitea
|
||||
##@ Gitea compatibility
|
||||
|
||||
gitea-deploy: ## Deploy / upgrade Gitea (S5 workload)
|
||||
helm upgrade --install $(GITEA_RELEASE) $(GITEA_CHART) \
|
||||
-f <(sops -d $(GITEA_VALUES)) \
|
||||
-f $(GITEA_REGISTRY_VALUES) \
|
||||
--namespace $(GITEA_NAMESPACE) --create-namespace
|
||||
gitea-deploy: ## Compatibility wrapper; Gitea deploy ownership moved to railiance-forge
|
||||
$(MAKE) -C $(FORGE_REPO) GITEA_RELEASE=$(GITEA_RELEASE) GITEA_NAMESPACE=$(GITEA_NAMESPACE) gitea-deploy
|
||||
|
||||
gitea-ingress-deploy: ## Apply the Gitea OCI registry ingress
|
||||
kubectl apply -f $(GITEA_INGRESS)
|
||||
gitea-ingress-deploy: ## Compatibility wrapper; Gitea ingress ownership moved to railiance-forge
|
||||
$(MAKE) -C $(FORGE_REPO) GITEA_RELEASE=$(GITEA_RELEASE) GITEA_NAMESPACE=$(GITEA_NAMESPACE) gitea-ingress-deploy
|
||||
|
||||
gitea-status: ## Check Gitea health
|
||||
kubectl get pods -n $(GITEA_NAMESPACE) -l app.kubernetes.io/instance=$(GITEA_RELEASE)
|
||||
kubectl get svc -n $(GITEA_NAMESPACE) $(GITEA_RELEASE)
|
||||
kubectl get ingress -n $(GITEA_NAMESPACE) $(GITEA_RELEASE) --ignore-not-found
|
||||
@if kubectl cnpg status gitea-db -n databases >/dev/null 2>&1; then \
|
||||
kubectl cnpg status gitea-db -n databases; \
|
||||
else \
|
||||
echo "kubectl cnpg plugin not available; falling back to cnpg resources"; \
|
||||
kubectl get cluster gitea-db -n databases; \
|
||||
kubectl get pods -n databases -l cnpg.io/cluster=gitea-db; \
|
||||
fi
|
||||
gitea-status: ## Compatibility wrapper; Gitea status ownership moved to railiance-forge
|
||||
$(MAKE) -C $(FORGE_REPO) GITEA_RELEASE=$(GITEA_RELEASE) GITEA_NAMESPACE=$(GITEA_NAMESPACE) gitea-status
|
||||
|
||||
apps-pg-status: ## Check the shared apps-pg cnpg cluster
|
||||
@if kubectl cnpg status apps-pg -n databases >/dev/null 2>&1; then \
|
||||
|
||||
Reference in New Issue
Block a user