bea103a280
Problem: Job ran on every ArgoCD sync, creating duplicate runners in Gitea. Solution: - initContainer gets token + saves to PVC (/data/.registration-token) - Runner container registers once, persists .runner file in PVC - Subsequent restarts skip registration (idempotent) - PVC runner-data (1Gi) persists registration across pod restarts - Removed register-job.yaml, moved RBAC to rbac.yaml - Runner waits for DinD before starting - Stable runner name: test-env-runner - Labels: edt + ubuntu-latest
19 lines
673 B
YAML
19 lines
673 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
resources:
|
|
# NOTE: namespace.yaml removed — ArgoCD creates namespace via syncOptions.CreateNamespace
|
|
# The namespace is shared with kargo-test-env-pipeline app.
|
|
# PostgreSQL 18.x-2.1C (image has built-in 1C entrypoint)
|
|
- postgres/statefulset.yaml
|
|
- postgres/service.yaml
|
|
# 1C:Enterprise server (ragent + crserver + ras)
|
|
- onec-server/statefulset.yaml
|
|
- onec-server/service.yaml
|
|
- onec-server/service-nodeport.yaml
|
|
- onec-server/configmap.yaml
|
|
# Gitea Actions runner (for apk-ci-ng workflows)
|
|
- gitea-runner/deployment.yaml
|
|
- gitea-runner/configmap.yaml
|
|
- gitea-runner/rbac.yaml
|