Repository navigation
fix(helm): expose authenticated native HTTP - #3427
Merged
Merged
Conversation
added 7 commits
October 28, 2026 09:51
3 of 9 tasks
imbajin
commented
Oct 28, 2026
bitflicker64
left a comment
Contributor
There was a problem hiding this comment.
Blocking: yes. Summary: easy mode now publishes the SeaTunnel and Vermeer HTTP entries on NodePort, but their generated passwords stay 6 characters, which online guessing can break on a node-reachable port.
MrJs133
approved these changes
Oct 28, 2026
This was referenced Oct 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before → After
SeaTunnel and Vermeer native HTTP entries remain private in easy mode because their Services and ingress policies are internal-only. This change makes their authenticated HTTP entries inherit NodePort in easy mode and ClusterIP in strict mode, while preserving explicit Service overrides.
Only SeaTunnel HTTP and Vermeer Master HTTP become reachable through the selected Service type. Worker HTTP, gRPC and member traffic remain private. Authentication, generated credentials, default-disabled components, topology selection and backend access remain unchanged. Chart validation, access instructions and regression coverage are updated together.
Validation
The source PR reports 82 Python regressions, 342 Helm assertions, preset lint/render checks, reactor compilation and bounded authentication/CNI checks. Backend TCP probes use mock listeners rather than a repeated full backend protocol scan. These are author-reported results, not independent ASF acceptance; upstream CI will run separately.
Source and detailed validation: hugegraph#350
Visual overview
Native HTTP access follows the resolved Service type: easy defaults to NodePort and strict to ClusterIP, while explicit overrides take precedence. Authentication remains required. This diagram describes routing, not security or live-cluster acceptance; the credential and plaintext-HTTP review remains a separate deployment consideration.