* feat(test-env): add 1C test environment manifests (#11) - PostgreSQL 18.x-2.1C StatefulSet with ru_RU.UTF-8 locale init - 1C server (ragent+crserver+ras) StatefulSet with stable hostname - Gitea runner Deployment with edt label for apk-ci-ng - NodePort services for external 1C access (31540-31545) - Deploy/verify script: dev/deploy-test-env.sh - config.yaml for ApplicationSet integration - test-env only in dev cluster (not in prod AppSet) * fix(test-env): use initContainer for PG data + remove custom entrypoint PVC mount on /var/lib/postgresql wipes the image's pre-built cluster. Solution: initContainer copies cluster data from image to PVC on first run. Removed custom pg-entrypoint.sh ConfigMap — image has its own. * feat(test-env): DinD sidecar for runner + auto-registration Job - Add Docker-in-Docker sidecar to gitea-runner Deployment - Add register-job.yaml: Job that obtains Gitea runner token via API, creates Secret, and scales runner to 1 - RBAC: ServiceAccount + Role/ClusterRole for cross-namespace secret access - Runner labels: edt (for apk-ci-ng), ubuntu-latest --------- Co-authored-by: XoR <xor@benadis.ru>
23 lines
785 B
YAML
23 lines
785 B
YAML
# Placeholder for SOPS-encrypted secrets
|
|
# Actual secrets will be encrypted with: sops --encrypt --age <admin-key>,<dev-key>
|
|
#
|
|
# Required secrets (create as test-env-secrets):
|
|
# pg-password: password for PostgreSQL usr1cv8 user
|
|
#
|
|
# Required secrets (create as test-env-runner-token):
|
|
# token: Gitea Actions runner registration token
|
|
#
|
|
# Example (before encryption):
|
|
# apiVersion: v1
|
|
# kind: Secret
|
|
# metadata:
|
|
# name: test-env-secrets
|
|
# namespace: test-env
|
|
# type: Opaque
|
|
# stringData:
|
|
# pg-password: "usr1cv8"
|
|
#
|
|
# For now, create secrets manually in the cluster:
|
|
# kubectl -n test-env create secret generic test-env-secrets --from-literal=pg-password=usr1cv8
|
|
# kubectl -n test-env create secret generic test-env-runner-token --from-literal=token=<TOKEN>
|