Hey there! Let's break down your two Kubernetes pod deletion questions clearly:

Kubernetes doesn’t have a built-in kubectl delete flag to filter pods directly by creation time, but we can combine kubectl with jq (a lightweight JSON processor) to get this done easily. Here are common scenarios:

• Delete pods older than a specific duration (e.g., 24 hours)
  Run this command to target pods created more than one day ago:

  kubectl get pods -o json | jq -r '.items[] | select(.metadata.creationTimestamp | fromdate < (now - 86400)) | .metadata.name' | xargs kubectl delete pod
  

  Let me break this down:

  • kubectl get pods -o json outputs all pod data in JSON format
  • jq -r ... filters the JSON to only include pods where the creation timestamp (converted to a Unix timestamp) is older than "now minus 86400 seconds" (which equals 1 day)
  • xargs kubectl delete pod passes the filtered pod names to the delete command

  Adjust the second count for different durations: e.g., 3600 for 1 hour, 604800 for 7 days.

• Delete pods created before a specific date/time
  First, convert your target date to a Unix timestamp (use date +%s on Linux/macOS). For example, to delete pods created before November 1st, 2023 (timestamp 1698806400), use:

  kubectl get pods -o json | jq -r '.items[] | select(.metadata.creationTimestamp | fromdate < 1698806400) | .metadata.name' | xargs kubectl delete pod
  

Absolutely! Orphaned pods are those not managed by any controller (like Deployment, StatefulSet, or DaemonSet)—you can spot them by checking their metadata.ownerReferences field is empty.

To delete only these isolated pods that are older than 1 day, use this command:

kubectl get pods -o json | jq -r '.items[] | select(.metadata.ownerReferences | length == 0) | select(.metadata.creationTimestamp | fromdate < (now - 86400)) | .metadata.name' | xargs kubectl delete pod

The extra select(.metadata.ownerReferences | length == 0) clause ensures we only target pods with no parent controller. Since you confirmed these pods won’t be recreated, deleting them is completely safe—there’s no controller that will spin up replacements.

Quick Notes #

• If working in a specific namespace, add -n <namespace> to every kubectl command (e.g., kubectl get pods -n my-namespace -o json)
• Preview which pods will be deleted first by running the command without the final | xargs kubectl delete pod step
• If you don’t have jq installed, grab it via your package manager (e.g., apt install jq on Debian/Ubuntu, brew install jq on macOS)

内容的提问来源于stack exchange，提问作者dansl1982