Service Publishing

Overview

Expose HTTP services running inside worker containers to the outside world via the Higress gateway. Each exposed port gets an auto-generated domain name.

How It Works

Add expose to a Worker's spec to publish container ports. The controller automatically creates the Higress domain, service source, and route.

Auto-generated domain pattern:

worker-{name}-{port}-local.hiclaw.io

Example: worker alice exposing port 8080 → worker-alice-8080-local.hiclaw.io

Usage

Via CLI

# Expose port 8080 for worker alice
hiclaw apply worker --name alice --model qwen3.5-plus --expose 8080

# Expose multiple ports
hiclaw apply worker --name alice --model qwen3.5-plus --expose 8080,3000

# Check exposed ports
hiclaw get worker alice
# Look for status.exposedPorts in the output

# Remove exposed ports (update without --expose)
hiclaw apply worker --name alice --model qwen3.5-plus

Via YAML

apiVersion: hiclaw.io/v1beta1
kind: Worker
metadata:
  name: alice
spec:
  model: qwen3.5-plus
  expose:
    - port: 8080
    - port: 3000

Apply with:

hiclaw apply -f worker.yaml

Team Workers

Team workers also support expose:

apiVersion: hiclaw.io/v1beta1
kind: Team
metadata:
  name: dev-team
spec:
  leader:
    name: lead
    model: qwen3.5-plus
  workers:
    - name: backend
      model: qwen3.5-plus
      expose:
        - port: 8080
    - name: frontend
      model: qwen3.5-plus
      expose:
        - port: 3000

Important Notes

The worker container must be running and the service must be listening on the specified port before it can be accessed
Domains are auto-generated; custom domains are not yet supported
No authentication is configured on exposed routes (public access)
Docker DNS resolves the worker container name (hiclaw-worker-{name}) automatically within hiclaw-net
To stop exposing a port, remove it from the expose list and re-apply

service-publishing