iac/apps/rfi/ugok/celery.yaml
ivan 742a811313 ugok: rebuild all apps as standalone HelmReleases, drop vault-native base
Root cause: apps/*/ugok extended ../base via kustomize patches, but base
is vault-native (Vault Agent Injector annotations + serviceAccount +
command/args wrapper sourcing /vault/secrets/*). The Vault Agent Injector
webhook IS deployed cluster-wide in ugok (infrastructure/vault/ugok), so
it actually intercepted these pods — but no per-app Vault roles/secrets
were ever provisioned there, so every pod hung in Init.

Fix, mirrored from apps/*/wb (which never extends base for these apps):
rebuild every affected app as a standalone HelmRelease per service, with
no serviceAccount/podAnnotations override and no vault-sourcing wrapper
in command/args (dropped entirely, or replaced with the real functional
command where base's wrapper did double duty — e.g. celery invocations,
pm's `python manage.py migrate`, pdf-markings-amqp's `start-amqp-worker`).

Also recreates ConfigMaps that were referenced by name in volumes but
never actually captured into the repo (eav, subscriptions, pm, issues,
django) — copied verbatim from the cluster dump and verified byte-for-byte
against it.

Incidental bugs found and fixed along the way:
- message-hub was still extending base (missed in an earlier pass).
- system-log's patches targeted services.api/services.worker while base
  uses services.backend for both — would have produced duplicate
  Deployments per release, one of them permanently vault-broken.
- contracts' real container port is 8080, not base's default 8000.
- drawings' Service.targetPort (8000) didn't match the real containerPort
  (8080), breaking routing.
- inspections/ugok was missing entirely from this pass.

apps/documentations: intentionally left without a redis Deployment even
though VALKEY_ADDR now points at one — the cluster dump has no redis in
that namespace, so provisioning one is a scope decision, not a bug fix.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-29 01:22:21 +05:00

176 lines
4.5 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
# standalone HelmRelease по образцу apps/rfi/wb/celery.yaml — base
# vault-native, в ugok Vault не используется. command/args — не
# vault-обёртка, а реальная команда запуска celery, сохранена как есть.
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
name: celery
namespace: rfi
spec:
interval: 10m
chart:
spec:
chart: universal-chart
version: "0.1.9"
sourceRef:
kind: HelmRepository
name: yc-oci-charts
namespace: flux-system
interval: 10m
install:
remediation:
retries: 3
upgrade:
remediation:
retries: 3
values:
global:
env: _default
services:
celery:
enabled: true
image:
name:
_default: 10.4.10.187:80/library/rfi-backend:production_79888e2f
pullPolicy:
_default: IfNotPresent
deployment:
enabled: true
name:
_default: celery
replicaCount:
_default: 1
port:
_default: 8000
command:
_default: ["uv"]
args:
_default: ["run", "celery", "-A", "config", "worker", "-l", "info"]
resources:
requests:
cpu:
_default: 25m
memory:
_default: 128Mi
probes:
liveness:
enabled: false
readiness:
enabled: false
service:
enabled: false
imagePullSecrets:
enabled:
_default: true
name:
_default: regcred
envs:
- name: JWT_AUTH_ENABLE
value:
_default: "True"
- name: NOTIFICATIONS_ENABLE
value:
_default: "false"
- name: NOTIFICATIONS_EMAIL_FROM
value:
_default: hello@sarex.io
- name: NOTIFICATIONS_SERVICE_URL
value:
_default: https://sarex.ugok.lan/rfi
- name: SAREX_BACKEND_URL
value:
_default: http://backend.django.svc.cluster.local:8000
- name: EAV_URL
value:
_default: http://eav-service.eav.svc.cluster.local:8000
- name: GATEWAY_URL
value:
_default: http://pdm-api.documentations.svc.cluster.local:8080
- name: RABBITMQ_PORT
value:
_default: "5672"
- name: RABBITMQ_HOST
value:
_default: rabbitmq.rabbitmq.svc.cluster.local
secretEnvs:
- name: DJANGO_SECRET_KEY
secretName:
_default: django-secret
secretKey: django_secret_key
- name: DB_HOST
secretName:
_default: rfi-postgresql-secret
secretKey: host
- name: DB_PORT
secretName:
_default: rfi-postgresql-secret
secretKey: port
- name: DB_NAME
secretName:
_default: rfi-postgresql-secret
secretKey: database
- name: DB_USER
secretName:
_default: rfi-postgresql-secret
secretKey: username
- name: DB_PASSWORD
secretName:
_default: rfi-postgresql-secret
secretKey: password
- name: SAREX_BACKEND_AUTH
secretName:
_default: django-secret
secretKey: token
- name: YC_S3_ACCESS_KEY_ID
secretName:
_default: rfi-s3-secret
secretKey: access_key
- name: YC_S3_SECRET_ACCESS_KEY
secretName:
_default: rfi-s3-secret
secretKey: secret_key
- name: YC_S3_BUCKET_NAME
secretName:
_default: rfi-s3-secret
secretKey: bucket
- name: YC_S3_ENDPOINT_URL
secretName:
_default: rfi-s3-secret
secretKey: endpoint
- name: RABBITMQ_VHOST
secretName:
_default: rfi-rabbitmq-secret
secretKey: vhost
- name: RABBITMQ_USERNAME
secretName:
_default: rfi-rabbitmq-secret
secretKey: username
- name: RABBITMQ_PASSWORD
secretName:
_default: rfi-rabbitmq-secret
secretKey: password
commitSha: ""
gitlabUri: ""
gitlabJobUrl: ""
owner: ""