Diagram
A decision tree showing how GKE Autopilot evaluates Pod resource requests at creation: it applies defaults for missing requests, raises requests below minimums such as 50m CPU, fixes CPU-to-memory ratios, handles ephemeral storage range violations, and either modifies and accepts the workload or rejects it.
How Autopilot Fixes Missing or Invalid Requests
Automatic resource management in Autopilot modifies workload configuration at creation to meet minimums, maximums, and ratios. Autopilot first applies default requests to containers with no request, then checks minimums and the CPU-to-memory ratio. The corrections work as follows:
Domain 9 of 12
24 practice questions
Practice this DomainLast updated