Track k8s manifest; teach make sync to mirror deployment/
CI / ci (push) Failing after 32s
Deploy / build-and-deploy (push) Failing after 5s

The flights-front deploy repo ships k8s manifests at deployment/k8s/,
a sibling of Aeroflot.Flights.Front/. Previously the sync script only
copied the app source, so any env change landed on the k8s side had
to be hand-edited in the deploy repo and was never reflected back.

- Bring deployment/k8s/flights-ui.yaml into this repo (with the new
  MAP_TILE_URL env pointing at flights.test.aeroflot.ru) so the
  cluster config lives next to the code that reads it.
- sync-to-flights-front.sh resolves the deploy-repo root from the
  target path and mirrors this repo's deployment/ directory there,
  mkdir'ing and copying contents without wiping unrelated files.
- Bump step numbering (1/6..6/6) and the summary now lists the synced
  deployment files in addition to the app files.
This commit is contained in:
2026-04-18 22:51:26 +03:00
parent 6813bf902e
commit 496a72e7d7
2 changed files with 79 additions and 10 deletions
+40
View File
@@ -0,0 +1,40 @@
apiVersion: apps/v1
kind: Deployment
metadata:
name: $AFL_PRJ_NAME
spec:
selector:
matchLabels:
name: $AFL_PRJ_NAME
template:
metadata:
labels:
name: $AFL_PRJ_NAME
spec:
nodeSelector:
kubernetes.io/os: linux
containers:
- name: $AFL_PRJ_NAME
image: $REGISTRY_SERVER/aeroflot.$K8NAMESPACE.$ENVIRONMENT/$AFL_PRJ_NAME:v$VERSION.$BUILD_NUMBER
ports:
- containerPort: 8080
resources:
limits:
memory: "256Mi"
cpu: "1000m"
requests:
memory: "64Mi"
cpu: "100m"
env:
- name: NODE_ENV
value: production
- name: ENVIRONMENT
value: $ENVIRONMENT
# flights-ui.devwebzavod.ru has no /map/api/** ingress rule, so
# point Leaflet at the upstream tile service that the real
# Aeroflot ingress serves (flights.test.aeroflot.ru terminates
# /map/api/** correctly). Override per-cluster if a different
# tile source is required.
- name: MAP_TILE_URL
value: https://flights.test.aeroflot.ru/map/api/tile/{z}/{x}/{y}.jpeg
$IMAGE_PULL_SECRETS