Skip to content

docs(k0s): align SAIA exposure guidance — NodePort as portable default#111

Merged
kupratyu-splunk merged 4 commits into
mainfrom
k0s-script-additional-logs
Jun 16, 2026
Merged

docs(k0s): align SAIA exposure guidance — NodePort as portable default#111
kupratyu-splunk merged 4 commits into
mainfrom
k0s-script-additional-logs

Conversation

@kbhos-splunk

Copy link
Copy Markdown
Collaborator

Description

Related Issues

  • Related to #

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)
  • Performance improvement
  • Test improvement
  • CI/CD improvement
  • Chore (dependency updates, etc.)

Changes Made

Testing Performed

  • Unit tests pass (make test)
  • Linting passes (make lint)
  • Integration tests pass (if applicable)
  • E2E tests pass (if applicable)
  • Manual testing performed

Test Environment

  • Kubernetes Version:
  • Cloud Provider:
  • Deployment Method:

Test Steps

Documentation

  • Updated inline code comments
  • Updated README.md (if adding features)
  • Updated API documentation
  • Updated deployment guides
  • Updated CHANGELOG.md
  • No documentation needed

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published
  • I have updated the Helm chart version (if applicable)
  • I have updated CRD schemas (if applicable)

Breaking Changes

Impact:

Migration Path:

Screenshots/Recordings

Additional Notes

Reviewer Notes

Please pay special attention to:


Commit Message Convention: This PR follows Conventional Commits

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the k0s cluster setup configuration to change how the SAIA “public” service is exposed and to clarify the intended exposure options (NodePort vs LoadBalancer/MetalLB) in the k0s installer context.

Changes:

  • Switch the default SAIA serviceTemplate.type from LoadBalancer to NodePort and introduce a fixed nodePort value.
  • Update the SAIA public exposure guidance comments to describe when to use NodePort vs MetalLB-backed LoadBalancer.
  • Disable MetalLB installation by default (metallb.install: false) and expand the MetalLB usage notes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread tools/cluster_setup/k0s-cluster-config.yaml Outdated
Comment thread tools/cluster_setup/k0s-cluster-config.yaml
Resolve contradictory messaging between the config template and the
installer: the config comment block now presents NodePort as the
default/portable option (works on cloud VPCs where MetalLB L2 cannot)
and frames LoadBalancer+MetalLB as the bare-metal-only alternative.
Replace the stale 'NodePort exposure is discouraged' WARNING in the
installer with an informational line that prints the access URL.

Co-Authored-By: Claude <noreply@anthropic.com>
@kbhos-splunk kbhos-splunk changed the title feat(): K0s script additional logs docs(k0s): align SAIA exposure guidance — NodePort as portable default Jun 16, 2026
@kupratyu-splunk kupratyu-splunk merged commit 7621a7b into main Jun 16, 2026
10 checks passed
@kupratyu-splunk kupratyu-splunk deleted the k0s-script-additional-logs branch June 16, 2026 10:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants