apache / apache/incubator-seata
k8s容器部署server,nacos注册模式下外部通讯问题
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
## Why you need it?
Is your feature request related to a problem? Please describe in details
k8s容器部署server ,注册中心和配置中心都使用nacos模式,外部服务无法通过nacos注册表中的pod 通讯,使用socks 代理也没有用。
## How it could be?
可通过设置jvm 参数socksProxyIp socksProxyPort 代理ip 和 端口来访问容器内的 seata server
## Other related information
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
Start by reproducing the Kubernetes deployment with Nacos used for registration and configuration, then inspect how the Seata server exposes its registered pod address and applies JVM SOCKS proxy settings. Done means an external service can communicate with the containerized Seata server through the proposed proxy IP and port configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100