Story Crater Bot
23fc334b8a
api.riotpiao.com has no in-cluster DNS record (getaddrinfo ENOTFOUND from inside the pod, confirmed against google.com resolving fine and kong-proxy.api.svc.cluster.local resolving fine) -- it only resolves via the home network's own DNS. Node's fetch/undici also silently drops a manually-set Host header (forbidden header per WHATWG fetch spec), so overriding Host per-request isn't viable either. hostAliases pinning the hostname to ingress-nginx-controller's ClusterIP lets pi's models.json baseUrl work completely unchanged -- TLS SNI/Host still say api.riotpiao.com so cert validation and Kong's Host-based routing both still work.
55 lines
1.5 KiB
YAML
55 lines
1.5 KiB
YAML
apiVersion: apps/v1
|
|
kind: Deployment
|
|
metadata:
|
|
name: agent-pod
|
|
namespace: agent-pod
|
|
spec:
|
|
replicas: 1
|
|
selector:
|
|
matchLabels:
|
|
app: agent-pod
|
|
template:
|
|
metadata:
|
|
labels:
|
|
app: agent-pod
|
|
spec:
|
|
# api.riotpiao.com has no in-cluster DNS record (only resolves from the
|
|
# home network's own resolver) -- pin it to ingress-nginx-controller's
|
|
# ClusterIP so pi's models.json baseUrl works unchanged. TLS still
|
|
# terminates correctly since SNI/Host still say api.riotpiao.com.
|
|
hostAliases:
|
|
- ip: "10.101.128.185"
|
|
hostnames:
|
|
- "api.riotpiao.com"
|
|
containers:
|
|
- name: pi
|
|
image: node:22-slim
|
|
command:
|
|
- sh
|
|
- -c
|
|
- "npm install -g @earendil-works/[email protected] && sleep infinity"
|
|
resources:
|
|
requests:
|
|
cpu: "2"
|
|
memory: 4Gi
|
|
limits:
|
|
cpu: "4"
|
|
memory: 8Gi
|
|
volumeMounts:
|
|
- name: pi-config
|
|
mountPath: /root/.pi/config.json
|
|
subPath: config.json
|
|
- name: pi-config
|
|
mountPath: /root/.pi/agent/settings.json
|
|
subPath: settings.json
|
|
- name: pi-models
|
|
mountPath: /root/.pi/agent/models.json
|
|
subPath: models.json
|
|
volumes:
|
|
- name: pi-config
|
|
configMap:
|
|
name: pi-config
|
|
- name: pi-models
|
|
secret:
|
|
secretName: pi-models
|