openclaw - 💡(How to fix) Fix k3s: add IOSG profile support to pod template [1 participants]

Fix Plan

To add support for the IOSG profile in the k3s pod template, follow these steps:

• Update pod template: Add a conditional mcp-dashboard container to openclaw/k8s/pod-template.yaml

spec:
  containers:
  - name: mcp-dashboard
    image: <mcp-dashboard-image>
    ports:
    - containerPort: 18790
    condition: {{ .Values.deployProfile == "iosg" }}

• Add service port mapping: Update the service to include port 18790

apiVersion: v1
kind: Service
spec:
  ports:
  - name: mcp-dashboard
    port: 18790
    targetPort: 18790

• Update IngressRoute: Add a route for <app-id>-18790.<cluster-domain>

apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
spec:
  routes:
  - match: Host(`{{ .Values.appId }}-18790.{{ .Values.clusterDomain }}`)
    kind: Rule
    services:
    - name: mcp-dashboard
      port: 18790

• Pass MCP_SERVERS_JSON env var: Update k3s.py to pass MCP_SERVERS_JSON as an env var to the pod Secret

import os

# ...

mcp_servers_json = os.environ.get('MCP_SERVERS_JSON')
if mcp_servers_json:
    pod_spec['env'] = [{'name': 'MCP_SERVERS_JSON', 'value': mcp_servers_json}]

• Profile-aware template selection: Use a separate template or conditional rendering in the deploy path to select the correct template based on the deploy profile.

Verification

To verify the fix, deploy the updated k3s pod template with the IOSG profile and check that the mcp-dashboard container is included and accessible on port 18790.

Extra Tips

• Make sure to update the docker-compose.iosg.yml file to match the changes made to the k3s pod template.
• Test the updated deploy path with different deploy profiles to ensure that the correct template is selected and the mcp-dashboard container is included only for the IOSG profile.