Cpu kubernetes bugs in google cloud

i’ve always this when deploy asp.net docker machine

Annotations: kubernetes.io/limit-ranger: LimitRanger plugin set: cpu request for container

complete msg

kubectl describe pods webapp3
Name: webapp3-76c89b8c76-sqxbz
Namespace: default
Priority: 0
PriorityClassName:
Node: gke-standard-cluster-2-default-pool-c6267173-5x3w/10.128.0.2
Start Time: Wed, 09 Oct 2019 01:37:16 +0200
Labels: app=webapp3
pod-template-hash=76c89b8c76
Annotations: kubernetes.io/limit-ranger: LimitRanger plugin set: cpu request for container webapplication3
Status: Running
IP: 10.4.0.18
Controlled By: ReplicaSet/webapp3-76c89b8c76
Containers:
webapplication3:
Container ID: docker://2cf13c3b95ca1a124d7ef4d7a1a359bc6903b4f57b2ede6ec51531a6bc700de9
Image: gcr.io/profound-gantry-248310/webapplication3
Image ID: docker-pullable://gcr.io/profound-gantry-248310/webapplication3@sha256:f1a4f7d2e07ed30b54c425fd2bfbf8df774a77c71793cadce78c4e3dc031ffbe
Port:
Host Port:
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Completed
Exit Code: 0
Started: Wed, 09 Oct 2019 01:37:18 +0200
Finished: Wed, 09 Oct 2019 01:37:18 +0200
Ready: False
Restart Count: 1
Requests:
cpu: 100m
Environment:

That just means that you did not set a CPU request for your pod. Am I missing the bug?