1 of 11

OpenClaw Jakarta Meetup

A Context-Aware Kubernetes�Desktop App + OpenClaw

OpenClaw Jakarta · 2026

by Aldi P Perdana

2 of 11

About Me

Who's talking

Solo Maker

Senior Software Engineer

Wego.com

GM IT Operations & Head of Engineering

Kompas Gramedia

OpenClaw Jakarta · 2026

3 of 11

Three products

Clawdtopia

OpenClaw as a service

Schemamotion

Native Mac OS App for Database Diagram Design

Kubemotion

Cross-platform Kubernetes desktop client, built with Rust and egui

Free and open-source desktop app to explore, debug, and manage your clusters

Today's Demo

OpenClaw Jakarta · 2026

What I’m Building

4 of 11

Problem

Kubernetes is powerful,�but the experience can be painful at times

01

Remembering kubectl flags

Resource names, flags, and context switching still live in your head.

02

Hunting across screens

Logs, events, rollout state. Scattered across tabs and commands.

03

Sharing context in incidents

Explaining "what I'm seeing" to a teammate is slower than it should be.

What engineers actually want

"Why is THIS failing?"

With context already attached. No copy-pasting.

One place to see → ask → act

No terminal / dashboard / Slack ping-pong.

Safe actions, clearly confirmed

Read first, optional writes with explicit confirmation.

OpenClaw Jakarta · 2026

5 of 11

The Idea

Put OpenClaw inside the K8s desktop app

Not "chat in Telegram." Chat that drives the interface.

Step 1

Click a resource

Pod / Deployment / Namespace becomes chat context automatically.

Step 2

Ask in plain language

"why is this crashing?"�"show previous logs"�"what changed?"

Step 3

UI reacts + answers

Opens logs/events, highlights problems, and offers next actions.

OpenClaw Jakarta · 2026

6 of 11

How it works

• Explorer + chat panel�• Resource context�• Action buttons

OpenClaw Jakarta · 2026

Architecture

Desktop App

OpenClaw Gateway

HTPP (chat/completions)

or

WebSocket

Kubernetes

• Auth + policy�• Tool allowlist�• Audit trail

• Kubeconfig

• Read: logs / events / describe�• Write: optional + confirmed

• RBAC

7 of 11

Chat capabilities that feel native

Must-Have (v1)

Auto context: cluster / namespace / selected resource

Read tools: logs, events, describe, rollout status

UI actions: open logs, jump to deployment, highlight failures

Action cards: "Open logs" · "Show events" · "Explain cause"

OpenClaw Jakarta · 2026

MVP

8 of 11

Live Demo

Click a resource → ask in plain language →�watch the UI do the work.

🖱️

Click pod

💬

Ask

UI reacts

9 of 11

Guardrails

Policy

• Tool allowlist. Start read-only�• RBAC maps to the user, no "god agent"�• Explicit confirm for all writes

Operations

• Audit trail: who asked + what executed�• Scopes: cluster / namespace / resource limits�• Rate limits + safe defaults

OpenClaw Jakarta · 2026

Security

10 of 11

Gateway hardening rules

01

Token or password auth

Set auth.mode: token or password

Don't skip it.

02

Bind to loopback

Keep Gateway local unless a proxy is truly needed.

03

Enable rate limiting

rateLimit:

maxAttempts: 10

windowMs: 60000

lockoutMs: 300000

exemptLoopback: true

gateway:� bind: loopback� auth: { mode: token, token: ${OPENCLAW_GATEWAY_TOKEN}, rateLimit:

maxAttempts: 10

windowMs: 60000

lockoutMs: 300000

exemptLoopback: true }� # trustedProxies: ["10.0.0.1"] # only if a proxy is in front

OpenClaw Jakarta · 2026

Security Config

11 of 11

OpenClaw Jakarta · 2026

Let’s Connect

Follow my X, I will share the Pro Version License of Kubemotion when it’s ready

Profile:� Linkedin: https://www.linkedin.com/in/aldidana/� Twitter/X: https://x.com/aldidana

Github: https://github.com/aldidana