The document discusses using HAProxy agents to solve maintenance issues with Kubernetes. It describes the old architecture of having multiple ingress controllers for health checks. Teams faced difficulties with too many backends making Kubernetes hard to maintain. HAProxy did not support gRPC health checks. The solution introduced is using HAProxy agents, which offloads health checks to non-ingress processes. This allows defining health checks directly in HAProxy configuration and simplifies maintenance. A demo is provided of quickly setting up agents.

1. 透過 HAProxy agent
解決 K8s 維護難題
Titansoft SRE Jeff
@ COSCUP 2022 lightning talk

2. 舊架構
Ingress-controller Ingress-controller
Ingress-controller
Ingress-controller
Ingress-controller
Ingress-controller
http-check /health

3. 團隊遭遇困難
• Backend 太多，k8s 維護麻煩
• HAProxy 尚未支援 grpc healthcheck
X8

4. K8s HAProxy agent
https://www.haproxy.com/documentation/hapee/latest/load-balancing/health-checking/agent-checks/

5. K8s HAProxy agent
https://www.haproxy.com/documentation/hapee/latest/load-balancing/health-checking/agent-checks/

6. 開始幹！
default-server agent-check agent-inter 1s agent-port 3000 agent-send "n"

7. 開始幹！
default-server agent-check agent-inter 1s agent-port 3000 agent-send "grpc mysvc.domain.com 443 grpc.health.v1.Health/Checkn"

8. 導入 agent
agent agent
agent agent
agent agent

9. 光速 DEMO