[helm] Enable external connectivity in the helm charts
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 97
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
### Description
Users should be able to enable external connectivity when deploying using Helm charts.
At the moment, the `CLIENT` protocol binds to the Helm service which is internal to the kubernetes system.
### Willingness to contribute
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the Helm charts and how the CLIENT protocol currently binds to its Kubernetes service. Determine the chart configuration and service exposure needed for external connectivity, then verify that a deployment can connect externally while preserving the existing internal deployment behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100