Cluster Explorer
Use Explorer inside a cluster when you need Kubernetes-level visibility without leaving Edka.
Path: Clusters -> your cluster -> Explorer
Explorer reads live Kubernetes resources from the selected cluster and groups them into operational views for workloads, networking, certificates, storage, configuration, access, Helm, namespaces, and nodes.
What Explorer shows
Section titled “What Explorer shows”Explorer includes:
- resource lists with namespace, health, search, and sort controls
- detail panels with overview, related resources, pods, YAML, logs, values, and container tabs where available
- Helm releases and Helm chart resources
- node inventory with node conditions, resource pressure, pod placement, and related workloads
Supported resources include pods, deployments, replica sets, stateful sets, daemon sets, jobs, cron jobs, services, endpoints, network policies, ingresses, Gateway API resources, cert-manager resources, PVCs, PVs, storage classes, ConfigMaps, Secrets, service accounts, RBAC resources, namespaces, nodes, Helm releases, and Helm charts.
Logs and manifests
Section titled “Logs and manifests”For pods and pod-backed resources, Explorer can show recent container logs directly in the detail panel.
The YAML (manifest) tab shows the live Kubernetes manifest for the selected resource. Use this when comparing what Edka configured with what is currently running in the cluster.
ConfigMap and Secret values
Section titled “ConfigMap and Secret values”Explorer can show ConfigMap values and Secret keys for supported resources. Secret values remain protected; sensitive reads require the same recent identity verification used by the Secrets workspace.
Use Secrets Management when you need to create, update, or delete Edka-managed user secrets.
Pod exec and debug containers
Section titled “Pod exec and debug containers”For pod troubleshooting, Explorer includes an exec workflow. When a target container does not have a useful shell, Edka can attach an ephemeral debug container from its debug toolbox image and then open a terminal session.
Use this for interactive inspection after checking the higher-level health, events, and logs. Debug sessions run inside the target cluster and should be treated like direct cluster access.
The Nodes view summarizes cluster nodes and their scheduled pods. It helps answer:
- which nodes are not ready
- where a workload is scheduled
- which pods are running on a node
- which workloads are affected by node pressure or placement
For aggregate health and resource pressure, use Cluster Monitoring. For warning events and K3s signals, use Cluster Diagnostics.
Access
Section titled “Access”Explorer requires cluster read access. Actions that mutate resources or open interactive sessions require the corresponding cluster permission and may be blocked on archived clusters.