“transport disconnect close” when use socketio&socketio-redisadapter,nginx ingress in k3s
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 63.2k
- Forks
- 10.3k
- Avg merge
- 11d 20h
- Merged PRs (30d)
- 2
Description
this is error report

this is my ingress config
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: CI_PROJECT_NAME
annotations:
kubernetes.io/ingress.class: "nginx"
#nginx.ingress.kubernetes.io/ssl-redirect: "true"
#nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
#nginx.ingress.kubernetes.io/use-regex: "true"
#nginx.ingress.kubernetes.io/proxy-body-size: 100m
# ip hash
nginx.ingress.kubernetes.io/upstream-hash-by: "$http_x_forwarded_for"
spec:
tls:
- hosts:
- HOST_URL
secretName: cluster-holyyun-tls
rules:
- host: HOST_URL
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: CI_PROJECT_NAME
port:
number: 3000
It`s worked sometimes,but when the client connected a span,this error happen。
this is my client&server config
socket = io(socketUrl + data.data.namespace, { query: { token: data.data.token, userId: userId }, transports: ["polling", "websocket"] })
io.adapter(createAdapter(pubClient, subClient));
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided NGINX Ingress configuration and the Socket.IO client and server setup using the Redis adapter. Reproduce the intermittent transport disconnect in the k3s environment, then determine whether the issue is in the ingress, transport selection, or adapter setup. Done means a confirmed cause and a documented configuration or code change that prevents the disconnect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, nginx, nodejs, redis, typescript
- Domain
- backend, devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100