让 nginx-ingress 在 Azure 中使用 UDP
Getting nginx-ingress to use UDP in Azure
目前此设置适用于 TCP,但一旦切换到 UDP,我就会收到错误
The Service "nginx-ingress-controller" is invalid: spec.ports: Invalid value:
[]core.ServicePort{core.ServicePort{Name:"proxied-udp-30001", Protocol:"UDP",
Port:30001, TargetPort:intstr.IntOrString{Type:0, IntVal:30001, StrVal:""},
NodePort:0}, core.ServicePort{Name:"proxied-udp-30002", Protocol:"UDP",
Port:30002, TargetPort:intstr.IntOrString{Type:0, IntVal:30002, StrVal:""},
NodePort:0}, core.ServicePort{Name:"http", Protocol:"TCP", Port:80,
TargetPort:intstr.IntOrString{Type:1, IntVal:0, StrVal:"http"}, NodePort:32724},
core.ServicePort{Name:"https", Protocol:"TCP", Port:443,
TargetPort:intstr.IntOrString{Type:1, IntVal:0, StrVal:"https"},
NodePort:30127}}: cannot create an external load balancer with mix protocols
在我尝试应用补丁之后
kubectl patch deployment nginx-ingress-controller -n ingress-nginx --patch $(Get-Content .\k8s\prod-azure-multi-pod-node\nginx-ingress-controller-deploy-patch.yaml -Raw)
kubectl patch svc nginx-ingress-controller -n ingress-nginx --patch $(Get-Content .\k8s\prod-azure-multi-pod-node\nginx-ingress-controller-svc-patch.yaml -Raw)
每个文件所在的位置
nginx-ingress-controller-svc-patch.yaml
apiVersion: v1
kind: Service
metadata:
annotations:
meta.helm.sh/release-name: nginx-ingress
meta.helm.sh/release-namespace: ingress-nginx
name: nginx-ingress-controller
namespace: ingress-nginx
selfLink: /api/v1/namespaces/ingress-nginx/services/nginx-ingress-controller
spec:
ports:
- name: proxied-udp-30001
port: 30001
targetPort: 30001
protocol: UDP
- name: proxied-udp-30002
port: 30002
targetPort: 30002
protocol: UDP
和 nginx-ingress-controller-deploy-patch.yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: nginx-ingress-controller
namespace: ingress-nginx
selfLink: /apis/extensions/v1beta1/namespaces/ingress-nginx/deployments/nginx-ingress-controller
spec:
template:
spec:
hostNetwork: true # Edit added via tutorial https://skryvets.com/blog/2019/04/09/exposing-tcp-and-udp-services-via-ingress-on-minikube/
containers:
- args:
- /nginx-ingress-controller
- --default-backend-service=ingress-nginx/nginx-ingress-default-backend
- --election-id=ingress-controller-leader
- --ingress-class=nginx
- --udp-services-configmap=default/udp-services # Needed for udp config map usage
- --configmap=ingress-nginx/nginx-ingress-controller
name: nginx-ingress-controller
服务看起来像这样
apiVersion: v1
kind: Service
metadata:
name: game-svc-1
namespace: default
spec:
selector:
instance: game-1
# type: NodePort
type: ClusterIP
ports:
- protocol: UDP
port: 9001 # exposed port
targetPort: 19132
和 Udp 配置文件
apiVersion: v1
kind: ConfigMap
metadata:
name: udp-services
namespace: default
data:
30001: "default/game-svc-1:9001"
30002: "default/game-svc-2:9002"
就像我说的那样,这在使用 tcp 时工作得很好,但是一旦我切换到 UDP,就会弹出错误,是否缺少 UDP 步骤?
编辑 > 添加微软声明的 helm 命令以使用 this command
helm install nginx-ingress stable/nginx-ingress --namespace ingress-nginx --set controller.replicaCount=2 --set controller.nodeSelector."beta\.kubernetes\.io/os"=linux --set defaultBackend.nodeSelector."beta\.kubernetes\.io/os"=linux --set controller.service.httpPort.enable=false --set controller.service.httpsPort.enable=false
查看错误,补丁似乎无法正确合并清单文件,因为从共享清单文件中丢失的错误提及的 TCP 端口可以看出这一点。
您可以尝试直接应用清单文件而不是使用补丁吗?
基于以下错误:
The Service "nginx-ingress-controller" is invalid: spec.ports: Invalid value:
[]core.ServicePort
{core.ServicePort{Name:"proxied-udp-30001", Protocol:"UDP", Port:30001, TargetPort:intstr.IntOrString {Type:0, IntVal:30001, StrVal:""}, NodePort:0},
core.ServicePort{Name:"proxied-udp-30002", Protocol:"UDP",
Port:30002, TargetPort:intstr.IntOrString{Type:0, IntVal:30002, StrVal:""},
NodePort:0},
core.ServicePort{Name:"http", Protocol:"TCP", Port:80,
TargetPort:intstr.IntOrString{Type:1, IntVal:0, StrVal:"http"}, NodePort:32724},
core.ServicePort{Name:"https", Protocol:"TCP", Port:443,
TargetPort:intstr.IntOrString{Type:1, IntVal:0, StrVal:"https"},
NodePort:30127}}:
错误准确地告诉您您正在尝试使用 PORT 类型的混合匹配来更新服务。
cannot create an external load balancer with mix protocols
这是因为 PATCH 命令将在现有配置(2 个 TCP 端口)之上添加配置(在您的情况下是 2 个新暴露的 UDP 端口)来扩充现有服务
从 TCP 转换为 UDP 的最佳方法是重用名称端口名称(http
和 https
),这将允许 PATCH 命令将字典条目合并在一起,替换TCP 并使用您的 UDP 端口设置注入 80/443。
如果您实际上希望同时支持 UDP/TCP,您需要将 ServiceType 更改为 ClusterIP
,因为 LoadBalancer
类型不支持协议不匹配单个 Public IP(Azure LoadBalancer 前端 IP)
目前此设置适用于 TCP,但一旦切换到 UDP,我就会收到错误
The Service "nginx-ingress-controller" is invalid: spec.ports: Invalid value:
[]core.ServicePort{core.ServicePort{Name:"proxied-udp-30001", Protocol:"UDP",
Port:30001, TargetPort:intstr.IntOrString{Type:0, IntVal:30001, StrVal:""},
NodePort:0}, core.ServicePort{Name:"proxied-udp-30002", Protocol:"UDP",
Port:30002, TargetPort:intstr.IntOrString{Type:0, IntVal:30002, StrVal:""},
NodePort:0}, core.ServicePort{Name:"http", Protocol:"TCP", Port:80,
TargetPort:intstr.IntOrString{Type:1, IntVal:0, StrVal:"http"}, NodePort:32724},
core.ServicePort{Name:"https", Protocol:"TCP", Port:443,
TargetPort:intstr.IntOrString{Type:1, IntVal:0, StrVal:"https"},
NodePort:30127}}: cannot create an external load balancer with mix protocols
在我尝试应用补丁之后
kubectl patch deployment nginx-ingress-controller -n ingress-nginx --patch $(Get-Content .\k8s\prod-azure-multi-pod-node\nginx-ingress-controller-deploy-patch.yaml -Raw)
kubectl patch svc nginx-ingress-controller -n ingress-nginx --patch $(Get-Content .\k8s\prod-azure-multi-pod-node\nginx-ingress-controller-svc-patch.yaml -Raw)
每个文件所在的位置
nginx-ingress-controller-svc-patch.yaml
apiVersion: v1
kind: Service
metadata:
annotations:
meta.helm.sh/release-name: nginx-ingress
meta.helm.sh/release-namespace: ingress-nginx
name: nginx-ingress-controller
namespace: ingress-nginx
selfLink: /api/v1/namespaces/ingress-nginx/services/nginx-ingress-controller
spec:
ports:
- name: proxied-udp-30001
port: 30001
targetPort: 30001
protocol: UDP
- name: proxied-udp-30002
port: 30002
targetPort: 30002
protocol: UDP
和 nginx-ingress-controller-deploy-patch.yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: nginx-ingress-controller
namespace: ingress-nginx
selfLink: /apis/extensions/v1beta1/namespaces/ingress-nginx/deployments/nginx-ingress-controller
spec:
template:
spec:
hostNetwork: true # Edit added via tutorial https://skryvets.com/blog/2019/04/09/exposing-tcp-and-udp-services-via-ingress-on-minikube/
containers:
- args:
- /nginx-ingress-controller
- --default-backend-service=ingress-nginx/nginx-ingress-default-backend
- --election-id=ingress-controller-leader
- --ingress-class=nginx
- --udp-services-configmap=default/udp-services # Needed for udp config map usage
- --configmap=ingress-nginx/nginx-ingress-controller
name: nginx-ingress-controller
服务看起来像这样
apiVersion: v1
kind: Service
metadata:
name: game-svc-1
namespace: default
spec:
selector:
instance: game-1
# type: NodePort
type: ClusterIP
ports:
- protocol: UDP
port: 9001 # exposed port
targetPort: 19132
和 Udp 配置文件
apiVersion: v1
kind: ConfigMap
metadata:
name: udp-services
namespace: default
data:
30001: "default/game-svc-1:9001"
30002: "default/game-svc-2:9002"
就像我说的那样,这在使用 tcp 时工作得很好,但是一旦我切换到 UDP,就会弹出错误,是否缺少 UDP 步骤?
编辑 > 添加微软声明的 helm 命令以使用 this command
helm install nginx-ingress stable/nginx-ingress --namespace ingress-nginx --set controller.replicaCount=2 --set controller.nodeSelector."beta\.kubernetes\.io/os"=linux --set defaultBackend.nodeSelector."beta\.kubernetes\.io/os"=linux --set controller.service.httpPort.enable=false --set controller.service.httpsPort.enable=false
查看错误,补丁似乎无法正确合并清单文件,因为从共享清单文件中丢失的错误提及的 TCP 端口可以看出这一点。 您可以尝试直接应用清单文件而不是使用补丁吗?
基于以下错误:
The Service "nginx-ingress-controller" is invalid: spec.ports: Invalid value:
[]core.ServicePort
{core.ServicePort{Name:"proxied-udp-30001", Protocol:"UDP", Port:30001, TargetPort:intstr.IntOrString {Type:0, IntVal:30001, StrVal:""}, NodePort:0},
core.ServicePort{Name:"proxied-udp-30002", Protocol:"UDP",
Port:30002, TargetPort:intstr.IntOrString{Type:0, IntVal:30002, StrVal:""},
NodePort:0},
core.ServicePort{Name:"http", Protocol:"TCP", Port:80,
TargetPort:intstr.IntOrString{Type:1, IntVal:0, StrVal:"http"}, NodePort:32724},
core.ServicePort{Name:"https", Protocol:"TCP", Port:443,
TargetPort:intstr.IntOrString{Type:1, IntVal:0, StrVal:"https"},
NodePort:30127}}:
错误准确地告诉您您正在尝试使用 PORT 类型的混合匹配来更新服务。
cannot create an external load balancer with mix protocols
这是因为 PATCH 命令将在现有配置(2 个 TCP 端口)之上添加配置(在您的情况下是 2 个新暴露的 UDP 端口)来扩充现有服务
从 TCP 转换为 UDP 的最佳方法是重用名称端口名称(http
和 https
),这将允许 PATCH 命令将字典条目合并在一起,替换TCP 并使用您的 UDP 端口设置注入 80/443。
如果您实际上希望同时支持 UDP/TCP,您需要将 ServiceType 更改为 ClusterIP
,因为 LoadBalancer
类型不支持协议不匹配单个 Public IP(Azure LoadBalancer 前端 IP)