Skip to content

docs: document exposing a workload on multiple host ports#542

Merged
talos-bot merged 1 commit into
siderolabs:mainfrom
utkuozdemir:docs/workload-proxy-multi-port
May 26, 2026
Merged

docs: document exposing a workload on multiple host ports#542
talos-bot merged 1 commit into
siderolabs:mainfrom
utkuozdemir:docs/workload-proxy-multi-port

Conversation

@utkuozdemir
Copy link
Copy Markdown
Member

The workload service proxy now accepts a comma-separated list of host port entries, optionally pairing each host port with a specific service port by number or name. Each entry produces its own exposed service with its own URL in Omni.

The label, prefix, and icon annotations gain per-host-port suffixed variants that override the unsuffixed one for a given host port.

Shipping in Omni 1.8. See siderolabs/omni#2771 and siderolabs/kube-service-exposer#18.

@utkuozdemir utkuozdemir requested a review from Copilot May 7, 2026 20:29
@utkuozdemir utkuozdemir self-assigned this May 7, 2026
@talos-bot talos-bot moved this to In Review in Planning May 7, 2026
@utkuozdemir
Copy link
Copy Markdown
Member Author

We should hold this until Omni 1.8 lands.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the Omni documentation for workload service proxying to reflect new support for exposing a single Kubernetes Service on multiple host ports, including per-host-port overrides for label/prefix/icon annotations.

Changes:

  • Updates the omni-kube-service-exposer.sidero.dev/port annotation docs to describe comma-separated host port entries and optional host-port:service-port mapping.
  • Adds a new “Exposing multiple host ports” section describing per-host-port suffixed annotations and behavior for prefix collisions.
  • Updates the “Access an exposed service” section to describe multi-host-port UI entries and prefix selection behavior.

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

Comment thread public/omni/cluster-management/expose-a-workload-via-service-proxy.mdx Outdated
Comment thread public/omni/cluster-management/expose-a-workload-via-service-proxy.mdx Outdated
@utkuozdemir utkuozdemir force-pushed the docs/workload-proxy-multi-port branch from 99ad547 to 365a640 Compare May 8, 2026 07:47
@github-project-automation github-project-automation Bot moved this from In Review to Approved in Planning May 12, 2026
The workload service proxy now accepts a comma-separated list of host port entries, optionally pairing each host port with a specific service port by number or name. Each entry produces its own exposed service with its own URL in Omni.

The label, prefix, and icon annotations gain per-host-port suffixed variants that override the unsuffixed one for a given host port.

Shipping in Omni 1.8. See siderolabs/omni#2771 and siderolabs/kube-service-exposer#18.

Signed-off-by: Utku Ozdemir <utku.ozdemir@siderolabs.com>
@utkuozdemir utkuozdemir force-pushed the docs/workload-proxy-multi-port branch from 365a640 to db59463 Compare May 26, 2026 08:45
@utkuozdemir
Copy link
Copy Markdown
Member Author

/m

@talos-bot talos-bot merged commit db59463 into siderolabs:main May 26, 2026
1 check passed
@github-project-automation github-project-automation Bot moved this from Approved to Done in Planning May 26, 2026
@utkuozdemir utkuozdemir deleted the docs/workload-proxy-multi-port branch May 26, 2026 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants