apache / apache/pulsar-manager
IPv6 Pulsar-manager deployment through helm chart
- Dominant language
- Vue
- Stars
- 539
- Forks
- 239
- PR merge metrics
- No merged PRs in 30d
Description
Hi Team,
We are doing IPv6 apache pulsar deployment. Zookeeper, proxy, bookie, broker, pulsar-manager,toolset, recovery deployed successfully through pulsar helm chart. All the communications are good except pulsar-manager. Nginx in pulsar manager accepting connections through IPv4 rather than IPv6.
We need to modify /etc/nginx/confi.d/default.conf listener and server from 9527 to [::]:9527 and 0.0.0.0 to [::]. Could someone please help to achieve this. Thanks in advance.
Attached screenshots for your reference.
Contributor guide
Research direction
Start by inspecting the Helm chart and the pulsar-manager container configuration that generates /etc/nginx/confi.d/default.conf. Reproduce the IPv6 deployment, then verify that the Nginx listener and server bind on IPv6 at port 9527 and that pulsar-manager is reachable over IPv6.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, nginx
- Domain
- devops, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100