Travel worker scheduling
The on-call owner needs the Unschedulable incident resolved for an original fictional workload. Retain status and diagnostic files, state the cause, repair the source definition and deliver a ready Pod with a checked recommendation. Don't remove unrelated resources.
A fictional travel worker remains Pending while its team waits for a scheduled export. The local node can't satisfy the requested CPU reservation. You'll preserve inventory and diagnostic evidence, separate scheduler placement from runtime memory failures, then prepare a corrected manifest with a request that fits the stated capacity. A smaller limit alone would leave the scheduling cause unchanged. Recreate the standalone Pod after its immutable definition changes and inspect the final ready state. The last step checks your operational recommendation as well as the repaired resource. This exercise uses fictional capacity in a deterministic local node, without changing real infrastructure.
kubectl get pods > status.txt
A worked first action on this original project fixture.