Kubernetes Workload Coverage
Right-sizing and cost visibility for cluster workloads, fed by a lightweight in-cluster agent — no inbound access to your cluster required.
How it works
A push-based agent feeds the same pipeline as every other resource type.
01
Inventory
Workloads (Deployments, StatefulSets, Nodes, …) are registered as they report in, pushed by the in-cluster agent.
02
Metrics
CPU/memory usage samples are buffered and averaged hourly, feeding the same trend analysis as any other resource type.
03
Optimization
Evaluates usage against requests/limits and turns findings into right-sizing recommendations.
Coverage by service
Inventory
Metrics
Optimization
Drift detection
Kubernetes
5 resource types
-
Kubernetes Namespaces
-
Kubernetes Nodes
-
Kubernetes Secrets
-
Kubernetes Service Accounts
-
Kubernetes Workloads
Configuration
- Go to Organization → Integrations → Kubernetes and register a cluster. This generates an agent token, shown once.
-
Install the agent with Helm, using the token and cluster ID from the previous step:
helm upgrade --install pruneops-k8s-agent oci://registry-1.docker.io/pruneops/k8s-agent-chart \ --version 0.4.0 \ --set pruneops.token=<TOKEN> \ --set pruneops.clusterId=<CLUSTER_ID> \ --namespace pruneops --create-namespace
- Wait a few minutes, then check the cluster list — "Last seen" updates once the agent starts reporting.