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.
23 lines
548 B
YAML
23 lines
548 B
YAML
apiVersion: v1
|
|
kind: Service
|
|
metadata:
|
|
name: prop
|
|
namespace: prop
|
|
spec:
|
|
type: ClusterIP
|
|
sessionAffinity: ClientIP
|
|
sessionAffinityConfig:
|
|
clientIP:
|
|
timeoutSeconds: 3600
|
|
selector:
|
|
app: prop
|
|
# Exclude prop-backfill (tier: backfill) — it runs PHX_SERVER=false
|
|
# and doesn't listen on :5000. A pre-tier-label deploy caused a
|
|
# Cloudflare 502 when ClientIP affinity pinned a source to the
|
|
# backfill endpoint.
|
|
tier: hot
|
|
ports:
|
|
- name: http
|
|
port: 5000
|
|
targetPort: 5000
|
|
protocol: TCP
|