Workload Details

Overview

Workload Details provides deep insights into individual workloads:

  • Cost Analysis - Total monthly cost breakdown by container and resource type
  • Resource Usage - Current and historical CPU/Memory utilization
  • Container Details - Per-container metrics and resource allocation
  • Optimization - Right-sizing recommendations with savings estimates
  • Performance - Request/limit efficiency and throttling detection
  • Configuration - YAML spec with best practices analysis

Access: Select cluster (Clusters page or sidebar dropdown) → Workloads → Select workload


Key Metrics

Monthly Cost Card:

  • Total cost with trend indicators with historical metrics
  • Breakdown: CPU (64%), Memory (27%), Storage (9%)
  • Ghost town analysis

Resource Efficiency:

  • CPU efficiency percentage (actual vs. requested)
  • Memory efficiency percentage
  • Over-provisioning amount in dollars/month

Replicas & Availability:

  • Current/desired replica count
  • Uptime percentage (historical)
  • Restart events (with reasons like OOMKilled)

Workload Type-Specific Features

Deployments:

  • Revision history and rollback capability
  • Rolling update status
  • HPA (autoscaler) configuration

StatefulSets:

  • Pod ordinal tracking
  • PVC bindings per pod
  • Storage cost per replica

DaemonSets:

  • Node distribution
  • Per-node pod status
  • Scheduling rules

Jobs/CronJobs:

  • Execution history
  • Cost per run
  • Failure analysis

Resource Charts

Interactive charts showing historical trends:

  • CPU Usage - Actual vs. requests vs. limits
  • Memory Usage - With OOM event markers
  • Network I/O - Inbound/outbound traffic
  • Disk I/O - Read/write operations

Features: Zoom, pan, export, annotations, comparison mode


Common Workflows

Right-Size a Workload:

  1. Check Resource Efficiency metrics
  2. Analyze historical usage charts
  3. Review Kubeadapt's recommendations
  4. Update via GitOps PR or kubectl patch
  5. Monitor after applying

Fix OOMKilled Pods:

  1. Check Availability card for restart count
  2. Analyze Memory chart for P99 usage
  3. Apply recommended limit increase
  4. Verify fix with monitoring