Graham McIntire
6c73012d09
Both the hot (`prop`) Deployment and the `prop-backfill` Deployment
labelled their pods with `app: prop` so both joined the same libcluster
Erlang cluster. The `prop` Service selector was `app: prop` too — which
meant the backfill pod (PHX_SERVER=false, no listener on :5000) was in
the Service endpoint pool.
With sessionAffinity: ClientIP, Cloudflared's source IP got hashed to
the backfill endpoint after a backfill pod roll and every request
from that client returned 502 (connection refused on :5000).
Fix: add `tier: hot` to hot-pod template labels; narrow the Service
selector to `{app: prop, tier: hot}`. Backfill keeps `tier: backfill`
and is cleanly excluded. libcluster selector (still `app: prop`) is
unchanged so backfill stays in the Erlang cluster for Oban queue
leader election and Oban.Pro's Smart engine.
|
||
|---|---|---|
| .. | ||
| deployment-backfill.yaml | ||
| deployment-grid-rs.yaml | ||
| deployment.yaml | ||
| flux.yaml | ||
| kustomization.yaml | ||
| metrics-service.yaml | ||
| namespace.yaml | ||
| rbac.yaml | ||
| service.yaml | ||