Receive gitea-values.sops.yaml from railiance-cluster — S5 now owns the Gitea deployment lifecycle per ADR-003 boundary rules. Add gitea-deploy and gitea-status Makefile targets. Update SCOPE.md to reflect boundary violation resolved. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
23 lines
671 B
Makefile
23 lines
671 B
Makefile
SHELL := /usr/bin/env bash
|
|
.DEFAULT_GOAL := help
|
|
|
|
##@ Gitea
|
|
|
|
gitea-deploy: ## Deploy / upgrade Gitea (S5 workload)
|
|
helm upgrade --install gitea gitea-charts/gitea \
|
|
-f <(sops -d helm/gitea-values.sops.yaml) \
|
|
--namespace gitea --create-namespace
|
|
|
|
gitea-status: ## Check Gitea health
|
|
kubectl get pods -n gitea
|
|
kubectl cnpg status gitea-db -n databases
|
|
|
|
##@ Help
|
|
|
|
help: ## Show this help
|
|
@awk 'BEGIN {FS = ":.*##"; printf "\nUsage:\n make \033[36m<target>\033[0m\n"} \
|
|
/^[a-zA-Z_-]+:.*?##/ { printf " \033[36m%-20s\033[0m %s\n", $$1, $$2 } \
|
|
/^##@/ { printf "\n\033[1m%s\033[0m\n", substr($$0, 5) }' $(MAKEFILE_LIST)
|
|
|
|
.PHONY: gitea-deploy gitea-status help
|