iac/apps/issues/uralkal
ivan c36406209f issues: SAREX_API from env, in-cluster Django in uralkal, vad, ugmk
The base production.py hardcoded SAREX_API = https://srx.wb.ru, ignoring the
env, so issue export (GET /api/core/users/<id>/) failed from closed contours
with CERTIFICATE_VERIFY_FAILED. Read it from SAREX_API with the old value as
default; wb keeps it.

uralkal, vad, d8-ugmk-prod: SAREX_API -> backend-svc.django:80 (server-side
calls, no TLS), and SAREX_HOST set to the contour's public host so links in
exports and notifications stay external.
2026-10-24 12:01:25 +05:00
..
backend-s3.yaml issues: SAREX_API from env, in-cluster Django in uralkal, vad, ugmk 2026-10-24 12:01:25 +05:00
backend.yaml uralkal: clear CPU/memory requests for all 36 business apps 2026-09-30 15:06:51 +03:00
celery-s3.yaml issues: SAREX_API from env, in-cluster Django in uralkal, vad, ugmk 2026-10-24 12:01:25 +05:00
celery.yaml uralkal: clear CPU/memory requests for all 36 business apps 2026-09-30 15:06:51 +03:00
frontend.yaml uralkal: clear CPU/memory requests for all 36 business apps 2026-09-30 15:06:51 +03:00
kustomization.yaml uralkal: take Kafka CA from the kafka-kafka-contour-tls secret 2026-10-06 21:59:43 +05:00