Repository navigation
docs(helm): explain authenticated native HTTP access - #551
Merged
Merged
Conversation
imbajin
force-pushed
the
docs/helm-vermeer
branch
2 times, most recently
from
October 28, 2026 12:11
e83d982 to
1c7a7f1
Compare
imbajin
force-pushed
the
docs/helm-vermeer
branch
from
October 28, 2026 12:19
1c7a7f1 to
b0afc78
Compare
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
Earlier sections of the bilingual Helm and Vermeer guides still describe native HTTP entries as private ClusterIP services in every mode. Document the proposed chart behavior: NodePort in easy mode, ClusterIP in strict mode, and explicit Service overrides taking precedence.
Add node-IP/HTTP-port discovery and login instructions while keeping Worker HTTP, RPC and member traffic private. Preserve the distinction between Service exposure and standalone/cluster topology, and pin the referenced Vermeer deployment guide.
Scope and validation
Documentation-only follow-up to Doc #550, aligned with Server #3427. The chart change and its credential-strength review remain pending. This PR does not claim released-chart availability, runtime isolation or RC acceptance. Checks reported for earlier branch revisions are not acceptance of this current head; current-head documentation CI runs separately.
Source: org Doc #55
Visual overview
Native HTTP access follows the final Service type, including explicit overrides: NodePort uses a reachable node address and assigned HTTP port; ClusterIP supports in-cluster access or authorized port-forwarding. Authentication remains required. This map describes intended access behavior; some current wording remains under review. It does not establish runtime isolation or security acceptance.