我有一个带有一个主节点和一个工作节点的 Kubernetes 集群设置。
通过从主机到 LoadBalancer 类型的 ingress-nginx 服务进行 NAT 将流量路由到集群,使用 MetalLb 设置:
#!/bin/bash
iptables -t nat -A PREROUTING -p tcp -i eth0 --dport 80 -j DNAT --to-destination "$1":80
iptables -A FORWARD -p tcp -d "$1" --dport 80 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT
$1
是 ingress-nginx 的外部 IP。
apiVersion: v1
kind: Service
metadata:
name: ingress-nginx
namespace: ingress-nginx
labels:
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/part-of: ingress-nginx
spec:
type: LoadBalancer
externalTrafficPolicy: Local
ports:
- name: http
port: 80
targetPort: 80
protocol: TCP
- name: https
port: 443
targetPort: 443
protocol: TCP
selector:
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/part-of: ingress-nginx
此时,如果我查看 ingress-nginx pod 的日志,我可以看到真实的源 IP 地址。
问题是当我检查从入口获取流量的下游应用程序的日志时,源 IP 是入口 pod 的 IP。
kind: Ingress
metadata:
namespace: laurkyt
name: laurkyt-ingress
annotations:
cert-manager.io/cluster-issuer: "letsencrypt-prod"
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
nginx.ingress.kubernetes.io/affinity: cookie
nginx.ingress.kubernetes.io/session-cookie-hash: sha1
nginx.ingress.kubernetes.io/session-cookie-name: REALTIMESERVERID
nginx.ingress.kubernetes.io/proxy-connect-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
nginx.ingress.kubernetes.io/send-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-body-size: 50m
ingress.kubernetes.io/proxy-body-size: 50m
spec:
tls:
- hosts:
- example.com
- '*.example.com'
secretName: wildcard-example-com
rules:
- host: example.com
http:
paths:
- backend:
serviceName: laurkyt
servicePort: 443
apiVersion: v1
kind: Service
metadata:
namespace: laurkyt
name: laurkyt
labels:
app: laurkyt
spec:
externalTrafficPolicy: Local
ports:
- port: 80
targetPort: 80
name: "http"
- port: 443
targetPort: 443
name: "https"
selector:
app: laurkyt
tier: laurkyt
有谁知道我为了在后端 pod 中保留源 IP 而缺少什么?