Kubernetes — ingress and load balancing¶
The ingress controller fulfils the load-balancer contract:
readiness-driven membership comes from the Service (pods leave the endpoints when
/api/ready fails), TLS from cert-manager, forwarded headers from the controller.
Traefik (k3s default)¶
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: lyndrix
annotations:
cert-manager.io/cluster-issuer: letsencrypt
traefik.ingress.kubernetes.io/router.entrypoints: websecure
spec:
ingressClassName: traefik
tls: [{ hosts: [lyndrix.example.com], secretName: lyndrix-tls }]
rules:
- host: lyndrix.example.com
http:
paths:
- path: /api/plugins/lyndrix.plugin.iac_orchestrator
pathType: Prefix
backend: { service: { name: lyndrix-runner, port: { number: 8081 } } }
- path: /
pathType: Prefix
backend: { service: { name: lyndrix-core, port: { number: 8081 } } }
SSE through Traefik needs no buffering changes; set
traefik.ingress.kubernetes.io/service.responseforwarding.flushinterval: "-1" on the Service if
you see delayed events.
ingress-nginx¶
metadata:
annotations:
nginx.ingress.kubernetes.io/proxy-buffering: "off"
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
Core settings¶
LYNDRIX_TRUSTED_PROXIES=<pod CIDR of the ingress controller> (the ingress pod
IPs change, their CIDR does not); LYNDRIX_UI_ENGINE=react. * also works, but
then every pod that can reach the core Service may forge X-Forwarded-For —
use it only together with a NetworkPolicy that admits the ingress alone (the
preflight reports * as a warning).