operations-workflows

Safely manage Kubernetes operations by enforcing consistent operation lifecycle, deterministic cleanup, and permission-gated behavior across logs, shell exec, port-forwarding, and node drain tasks. This ensures session state remains correct during cluster removal, auth failure, and cancellation.

Long-running Kubernetes debug containers trigger idempotent stop paths and deterministic cleanup when cluster removal, auth failure, or app shutdown occurs. The operation registry preserves correct session lifecycle semantics and cleans up resources automatically across these disconnect scenarios.

Yes, you can coordinate Kubernetes log workflows across multi-cluster environments. The skill handles cluster-scoped targeting metadata, object-scoped operations for pod logs, and stream lifecycles while maintaining visible permission and capability reasons for each operation.

Handle Kubernetes node drain maintenance by managing interactive maintenance state, tracking progress, and surfacing operation history to the UI. The workflow maintains correct frontend and backend state ownership boundaries aligned with documented workflow contracts.

Kubernetes shell exec sessions stay open when cleanup paths lack idempotent stop logic or proper operation registry behavior. The skill enforces deterministic cleanup across close, disconnect, cluster removal, auth failure, and app shutdown to prevent orphaned sessions.

Yes, Kubernetes debug container workflows require visible permission and capability checks before execution. The skill enforces permission-gated behavior with cluster-scoped targeting metadata, ensuring only authorized operations proceed with correct lifecycle semantics.