AIP-5158: add enterprise load balancer guide for SAIA and SLIM - #232
Merged
Merged
Conversation
Documents how to front the SAIA/SLIM NodePorts with a bring-your-own enterprise load balancer (TLS termination, health checks, and a separate SLIM backend pool) as a replacement for the SSH-bastion SOCKS tunnel access path.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 460cc64f70
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Distinguishes L4 (NLB) vs L7 (HAProxy/ALB) backend/routing behavior, adds single-node cluster guidance, splits SAIA/SLIM health checks, clarifies TLS termination vs mixed-content constraints, and adds nonstandard listener port notes across onboarding/verification steps.
kupratyu-splunk
changed the title
vavarshn
reviewed
Sep 17, 2026
vavarshn
reviewed
Sep 17, 2026
Cloud L4 load balancers don't uniformly support TLS termination (GCP's Network LB and Azure Load Balancer are pure passthrough), so scope the generic "cloud NLB" examples to AWS NLB specifically. Also soften the SOCKS-tunnel framing (it's the correct approach for single-engineer setup, not a flaw), tone down "supported and validated" to "recommended deployment pattern," and add a reverse link from k0s-readme.md's Service Template section back to this guide.
kbhos-splunk
approved these changes
Sep 17, 2026
vavarshn
approved these changes
Sep 17, 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
3 participants
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.
https://splunk.atlassian.net/browse/AIP-5158
Documents how to front the SAIA/SLIM NodePorts with a bring-your-own enterprise load balancer (TLS termination, health checks, and a separate SLIM backend pool) as a replacement for the SSH-bastion SOCKS tunnel access path.
Description
Related Issues
Type of Change
Changes Made
Testing Performed
make test)make lint)Test Environment
Test Steps
Documentation
Checklist
Breaking Changes
Impact:
Migration Path:
Screenshots/Recordings
Additional Notes
Reviewer Notes
Please pay special attention to:
Commit Message Convention: This PR follows Conventional Commits