Pick a technology or a problem space.
CoreTrailKitGUIDEInvestigate a Pending persistent volume claim by comparing capacity, storage class and selectors, then verify an appropriate binding without deleting existing data.
CoreTrailKitGUIDEDiagnose a missing Secret key before the container starts, inspect names without exposing credentials, and verify that the corrected reference allows startup.
CoreTrailKitGUIDEExplain why editing a ConfigMap does not refresh an existing container’s environment, verify the old and new values, and roll out the intended application revision.
CoreTrailKitGUIDEDiagnose an unscheduled Kubernetes Pod from its scheduler condition, distinguish CPU requests from current usage, and verify a workload that fits available capacity.
CoreTrailKitGUIDEExplain why a running Pod receives no Service traffic when its readiness probe gets HTTP 404, verify the intended endpoint, and restore readiness without removing checks.
CoreTrailKitGUIDETrace a Service port to the application listener, distinguish ready backends from a working port mapping, and verify a corrected targetPort with an in-cluster request.
CoreTrailKitGUIDEDiagnose a Service with no matching backends, compare its selector with Pod labels and EndpointSlices, and verify traffic after a narrowly scoped selector repair.
CoreTrailKitGUIDEUse previous-container logs and termination status to diagnose an application configuration failure, then verify the corrected workload rather than restarting blindly.
CoreTrailKitGUIDEInvestigate an OOMKilled container, distinguish its memory limit from scheduling requests, and verify a measured change without treating exit 137 as a diagnosis.
CoreTrailKitGUIDESeparate probe-triggered restarts from application crashes and OOM kills. Give initialization a measured startup budget without hiding real failures.