clean up dead Fiesta NATS gateway sidecar and its routing scraps

The "gateway" sidecar in the fiesta StatefulSet (workolik360/alaska image,
running fiesta-gateway-script) and the k8s routing objects meant to reach it
(fiesta-route HTTPRoute, the port-8000 rules in nearle-ingress) never
actually served real traffic. fiesta.nearle.app is routed by a standalone
Docker/nginx proxy (conf/nginx-fiesta.conf, unchanged since the initial
commit) straight to NodePort 30823 - the real backend, no path splitting.
The Kubernetes-native routing objects have no working controller on this
cluster (no Traefik/Envoy pod; the shared Gateway resource's own status is
"Waiting for controller"), so they were inert either way.

The sidecar's only real effect, when briefly reachable, was publishing
Fiesta orders onto the same NATS subject worker-orders drains - which
forwards to jupiter, not this backend - producing the header-only phantom
orders fixed in the app on 2026-07-29. It's not a working parallel path,
it was the source of that bug.

Removed: the gateway container + gateway-script volume from the fiesta
StatefulSet, port 8000 from the fiesta Service, the fiesta-route HTTPRoute,
the fiesta-gateway-script ConfigMap (fiesta-gateway.yaml deleted entirely),
and the two dead port-8000 path rules in nearle-ingress's fiesta host block
(kept the correct catch-all). queue.workolik.com and the core-namespace NATS
worker pipeline are untouched - separate system entirely.

Verified live: fiesta pods rolled to single-container, service has only
port 80, and a real request through fiesta.nearle.app still behaves
correctly post-cleanup.
This commit is contained in:
Suriya
2026-07-29 17:34:03 +05:30
parent 29751d2d3d
commit d98ebdd152
4 changed files with 7 additions and 599 deletions

View File

@@ -74,39 +74,6 @@ spec:
secretKeyRef:
name: nats-credentials
key: password
- name: gateway
image: workolik360/alaska:v1.2.0
imagePullPolicy: Always
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
ports:
- containerPort: 8000
name: http
volumeMounts:
- name: gateway-script
mountPath: /app/app.py
subPath: app.py
envFrom:
- configMapRef:
name: nearle-config
env:
- name: NATS_USER
valueFrom:
secretKeyRef:
name: nats-credentials
key: username
- name: NATS_PASSWORD
valueFrom:
secretKeyRef:
name: nats-credentials
key: password
volumes:
- name: gateway-script
configMap:
name: fiesta-gateway-script
---
apiVersion: v1
kind: Service
@@ -123,42 +90,5 @@ spec:
nodePort: 30823
protocol: TCP
name: main
- port: 8000
targetPort: 8000
name: gateway
protocol: TCP
selector:
app: fiesta
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: fiesta-route
namespace: nearle
labels:
app: fiesta
spec:
parentRefs:
- name: gateway
namespace: alaska
hostnames:
- "fiesta.nearle.app"
rules:
# mob/orders/createorder and web/products/create used to be routed to the
# NATS gateway sidecar (port 8000, ConfigMap fiesta-gateway-script). That
# sidecar publishes onto the shared "ORDERS"/"PRODUCTS" NATS subjects,
# whose only consumer (worker-orders/worker-products in the core namespace)
# has EXTERNAL_BASE_URL hardcoded to jupiter, not this backend. Fiesta has
# no NATS consumer of its own, so every order/product submitted through
# that path was silently created on jupiter (header-only, wrong schema)
# instead of ever reaching CreateOrderv3 here. Both paths are already
# registered directly on this backend (routes/orderroutes.go,
# routes/productroutes.go), so route them straight through synchronously
# via the catch-all rule below instead of overriding them to the sidecar.
- matches:
- path:
type: PathPrefix
value: /
backendRefs:
- name: fiesta
port: 80