Sealos Canvas

Identity and Discovery

• Owner: sealos-canvas (/sealos-canvas and deployed-resource view, inspect, visualize, topology, or localhost canvas requests).
• Class: read-only-observation with no downstream mutation handoff.
• Canaries: CANVAS-DEPLOYED, CANVAS-READONLY, CANVAS-REDACT, and CANVAS-SERVER-LIFETIME.

Scope and Boundaries

Require .sealos/state.json with last_deploy, ~/.sealos/kubeconfig, and live read access. Use only read commands such as kubectl get and kubectl config view; never deploy, update, restart, patch, delete, or apply. Render sanitized resource metadata into .sealos/canvas/index.html and return the exact local URL/cache and server-lifetime contract.

Risk and Confirmation

Keep the read-only boundary, Sealos kubeconfig scope, and Secret/ConfigMap sanitization visible before generator detail. Omit Secret.data and ConfigMap.data from every result. A missing state or kubeconfig stops the request without fallback generation. Never expose Secret data, complete ConfigMap contents, kubeconfig contents, or credentials.

Lifecycle Workflow

For each request, resolve the project, check deployed state and kubeconfig, run the single generator, open the loopback UI, and report sanitized counts. The temporary 127.0.0.1 server runs only for the current process and stops when the process ends or on SIGINT/SIGTERM; stop the server before closing the request.