MFCommander Infra
Inspect your cluster.
Work with its files.
Follow workloads into logs, terminals and volume files. Manage Kubernetes and Docker in the same two-pane workspace.
Uses the kubectl and kubeconfig you already have.
See what needs attention.
Start with cluster health, resource usage and events. Keep the overview beside the resources you are investigating.
Inspect a resource and follow its connections.
Open a resource to inspect its status, events and YAML. Follow related objects to understand how a workload connects to its pods, services and configuration.
Trace a pod back to its Deployment, inspect a referenced ConfigMap or open its logs without losing your place. Related lists link to the full resource list when there is more to see.
Logs from the Logs tab
Follow one pod's output, or select several and read them as a single merged stream, in the same viewer that opens a gigabyte file without loading it.
YAML you can edit
Read-only until you choose Edit, checked with a dry run before it applies, and refused while read-only mode is on. F3 opens it in the large-file viewer instead.
Monitoring
CPU, memory, network, and disk charts from Prometheus, found in your cluster automatically or pointed wherever you tell the connection to look. Metrics Server is the fallback.
Actions that know the kind
Scale a Deployment, restart a StatefulSet, evict a pod with its disruption budget respected, cordon or drain a node, suspend a CronJob. Nothing offered where it makes no sense.
Metrics in the lists
Pod and node lists carry live CPU and memory columns, with the last reading carried forward so a momentary gap does not blank the table.
Secrets, revealed deliberately
A Secret's keys are listed but not shown until you ask for one, so a glance over your shoulder does not become an incident.
View logs across multiple pods in a single window.
Read several pods in one stream, filter by pod or container, and follow new output as it arrives. Long sessions keep memory use bounded by storing the stream on disk. How the viewer works, and the measurements behind it.
Open a shell in the container you’re inspecting.
Select a Pod and choose Open Shell to run commands in one of its running containers. Keep the Pod list visible while you inspect files or check a command’s output.
Uses your existing cluster credentials and exec permissions. Requires Kubernetes writes enabled and a shell in the container.
Copy files into or out of a volume.
Open a persistent volume claim (PVC) with Browse Files. Inspect its contents in a file pane, then copy between the volume and your Mac, an SFTP server or an S3 bucket.
It goes through a pod you are already running that mounts the volume, and creates a short-lived helper only when there is none. Exactly what that pod is, and how it goes away.
Open a cluster service on your Mac.
Choose Port Forward on a Pod, Service, Deployment, StatefulSet, DaemonSet, or ReplicaSet. Pick a declared remote port and an available local port, or select Any free port to let kubectl choose. Select Open in browser when ready to open the page once the tunnel is listening.
Forwards belong to the app, not to the tab you started them from, so closing the tab leaves them running. Window ▸ Port Forwards lists their state and uptime. Dropped connections reconnect automatically, and quitting stops all forwards. Read-only mode allows port forwarding. The service you connect to controls what you can read or change.
Use the same tools with Docker.
Containers, Images, Volumes, and Networks, with an overview carrying counts, live CPU and memory, and where the disk went. Start, stop, restart, pause, kill, and remove containers. Pull and remove images. Follow container logs in the same viewer.
Volumes browse exactly like PVCs do. It drives the docker command you already have, with your current context, so whatever your CLI can reach, this can reach.
Browse built-in and custom resources.
Browse standard resource types and automatically discovered custom resources using your existing cluster permissions.
Cluster
Overview, Events, Nodes, Namespaces.
Workloads
Pods, Deployments, StatefulSets, DaemonSets, ReplicaSets, Jobs, CronJobs.
Config
Config Maps, Secrets, Resource Quotas, Limit Ranges, PDBs, HPAs, VPAs, Priority Classes.
Network
Services, Endpoints, Endpoint Slices, Gateways, Gateway Classes, HTTP Routes, Network Policies.
Storage
Persistent Volumes, Persistent Volume Claims, Storage Classes.
Helm
Read-only release browsing, including chart versions and status.
Access Control
Service Accounts, Roles, Cluster Roles, and both kinds of binding.
Custom Resources
The definitions, plus every discovered instance kind nested under its API group.
Read-only until you say otherwise.
Both browsers start read-only. Scaling, restarting, deleting, applying YAML, and writing to a volume are refused until you turn the guard off. Kubernetes API actions use your kubeconfig credentials and permissions.
The long version, written for whoever has to approve it, covers what runs in the cluster, where credentials live, and everything the application sends anywhere.
Point it at a cluster for fourteen days.
Every feature, no card, and read-only is already on. Infra is a one-time $99.99 and includes everything in Pro, so the same window also reaches your SMB shares, SFTP servers, and S3 buckets.