gpt4 book ai didi

nginx - 无法在非根上下文路径中通过 kubernetes ingress-nginx 使 websocket 应用程序工作

转载 作者:行者123 更新时间:2023-12-04 15:29:21 25 4
gpt4 key购买 nike

这是一个示例 WebSocket 应用程序,我试图让它从 Kubernetes ingress-nginx Controller 工作。

Kubernetes yaml:

echo "
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: ws-example
spec:
replicas: 1
template:
metadata:
labels:
app: wseg
spec:
containers:
- name: websocketexample
image: nicksardo/websocketexample
imagePullPolicy: Always
ports:
- name: http
containerPort: 8080
env:
- name: podname
valueFrom:
fieldRef:
fieldPath: metadata.name
---
apiVersion: v1
kind: Service
metadata:
name: ws-example-svc
labels:
app: wseg
spec:
type: NodePort
ports:
- port: 80
targetPort: 8080
protocol: TCP
selector:
app: wseg
---

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: ws-example-svc
annotations:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/rewrite-target: /
spec:
rules:
- host: myhostname.com
http:
paths:
- backend:
serviceName: ws-example-svc
servicePort: 80
path: /somecontext

" | kubectl create -f -

我收到此错误:
WebSocket connection to 'ws://myhostname.com/somecontext/ws?encoding=text' failed: Error during WebSocket handshake: Unexpected response code: 400

当我尝试使用这样的 WebSocket 客户端网页进行连接时 http://www.websocket.org/echo.html

ingress-nginx 的版本是 0.14.0。此版本支持 WebSockets。

更新,当我从本地主机端口转发到 pod 的端口时,我可以直接访问运行 pod 的 websocket。
[rpalaniappan@sdgl15280a331:~/git/zalenium] $ kubectl get pods -l app=wseg
NAME READY STATUS RESTARTS AGE
ws-example-5dddb98cfb-vmdt5 1/1 Running 0 5h
[rpalaniappan@sdgl15280a331:~/git/zalenium] $ kubectl port-forward ws-example-5dddb98cfb-vmdt5 8080:8080
Forwarding from 127.0.0.1:8080 -> 8080
Forwarding from [::1]:8080 -> 8080
Handling connection for 8080
[rpalaniappan@sdgl15280a331:~/git/zalenium] $ wscat -c ws://localhost:8080/ws
connected (press CTRL+C to quit)
< Connected to ws-example-5dddb98cfb-vmdt5
> hi
< hi
< ws-example-5dddb98cfb-vmdt5 reports time: 2018-12-28 01:19:00.788098266 +0000 UTC

最佳答案

所以基本上是这样的:

nginx.ingress.kubernetes.io/rewrite-target: /

正在剥 /ws来自每次浏览器尝试发出 WebSocket 连接请求时发送到后端的请求(与 path: /ws 结合)。后端期望 /ws当它收到连接请求时。

如果您指定 path: /mypath/mypath/*它有效(对我有用):
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: ws-example-svc
annotations:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/rewrite-target: /
spec:
rules:
- host: myhostname.com
http:
paths:
- backend:
serviceName: ws-example-svc
servicePort: 80
path: /mypath
- backend:
serviceName: ws-example-svc
servicePort: 80
path: /mypath/*

关于nginx - 无法在非根上下文路径中通过 kubernetes ingress-nginx 使 websocket 应用程序工作,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/53950918/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com