Kubernetes Deep Dive

Sign Up Free or Log In to participate!

Cluster autoscaled even after sufficient resources (CPU) available

I have a cluster (GKE) with 1 node of type N1 Standard (1 CPU). My deployment requests 1 replica of a container that requests .5 of 1 CPU.

spec:

containers:

  • image: nginx:1.12

    name: nginx

    resources:

    limits:

    cpu: 1

    requests:

    cpu: 0.5

When I deploy this, I expect that the pod should get created (enough resources available in the cluster, 1 CPU available and only .5 requested). But the pod goes in pending state and waits for cluster to scale up the nodes. The pod comes up with cluster scaled up to 3 nodes. Why 3 nodes when only 1 was sufficient?

This is the same example used by Nigel in the Cluster Autoscaling demo lesson.

Am I missing something?

0 Answers

Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!

Get Started
Who’s going to be learning?