Kubernetes & K3s

Open a kubeconfig, switch contexts and namespaces, list resources, read details and events, and fetch Pod logs with the RBAC each view needs.

• Connect to a cluster with a kubeconfig context

  Add a Kubernetes or K3s connection from a kubeconfig file, pick a context and default namespace, and see which authentication methods are supported.

• Choose a Kubernetes namespace

  Pick the namespace a Kubernetes or K3s tab queries, list across all namespaces with *, and keep working when you are not allowed to list namespaces.

• List Kubernetes resources with get

  Use the get <resource> [namespace] query to list Pods, Deployments, Services, ConfigMaps, events, nodes and namespaces in DevOpsPad, read-only.

• Inspect a Kubernetes resource

  Open a Pod, Deployment, Service or node in the resource inspector to see its status, labels, containers, restarts and the read-only JSON definition.

• View events for a Kubernetes resource

  See the Kubernetes events for one Pod, Deployment or node, matched by UID rather than name, with the 200-event and 1 MiB preview limits explained.

• Read Pod logs, including a crashed container

  Read a log snapshot for any application, init or ephemeral container in a Pod, choose how many lines to tail and see the previous instance after a crash.

• Kubernetes permissions DevOpsPad needs

  The Kubernetes RBAC verbs each DevOpsPad view needs, from testing a connection to reading Pod logs, plus a minimal read-only Role you can grant.

• Why exec-based kubeconfig auth fails

  DevOpsPad does not run kubeconfig exec plugins such as cloud CLI token helpers yet. See which contexts are affected and how to connect with a token instead.