<p>I am trying to install Kubectl but when I type this in the terminal :</p>

<pre><code>kubectl get pods --namespace knative-serving -w
</code></pre>

<p>I got this :</p>

<pre><code>NAME                          READY     STATUS    RESTARTS   AGE
activator-69b8474d6b-jvzvs    2/2       Running   0          2h
autoscaler-6579b57774-cgmm9   2/2       Running   0          2h
controller-66cd7d99df-q59kl   0/1       Pending   0          2h
webhook-6d9568d-v4pgk         1/1       Running   0          2h
controller-66cd7d99df-q59kl   0/1       Pending   0         2h
controller-66cd7d99df-q59kl   0/1       Pending   0         2h
controller-66cd7d99df-q59kl   0/1       Pending   0         2h
controller-66cd7d99df-q59kl   0/1       Pending   0         2h
controller-66cd7d99df-q59kl   0/1       Pending   0         2h
controller-66cd7d99df-q59kl   0/1       Pending   0         2h
</code></pre>

<p>I don't understand why <code>controller-66cd7d99df-q59kl</code> is still pending.</p>

<p>When I tried this : <code>kubectl describe pods -n knative-serving controller-66cd7d99df-q59kl</code> I got this :</p>

<pre><code>Name:           controller-66cd7d99df-q59kl
Namespace:      knative-serving
Node:           &lt;none&gt;
Labels:         app=controller
                pod-template-hash=66cd7d99df
Annotations:    sidecar.istio.io/inject=false
Status:         Pending
IP:             
Controlled By:  ReplicaSet/controller-66cd7d99df
Containers:
  controller:
    Image:  gcr.io/knative-releases/github.com/knative/serving/cmd/controller@sha256:5a5a0d5fffe839c99fc8f18ba028375467fdcd83cbee9c7015c1a58d01ca6929
    Port:   9090/TCP
    Limits:
      cpu:     1
      memory:  1000Mi
    Requests:
      cpu:        100m
      memory:     100Mi
    Environment:  &lt;none&gt;
    Mounts:
      /etc/config-logging from config-logging (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from controller-token-d9l64 (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  config-logging:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      config-logging
    Optional:  false
  controller-token-d9l64:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  controller-token-d9l64
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  &lt;none&gt;
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  40s (x98 over 2h)  default-scheduler  0/1 nodes are available: 1 Insufficient cpu.
</code></pre>

Bruce Peter
<p>Please consider the comments above: you have <code>kubectl</code> installed correctly (it's working) and <code>kubectl describe pod/&lt;pod&gt;</code> would help...</p>

<p>But, the information you provide appears sufficient for an answer:</p>

<p><code>FailedScheduling</code> because of <code>Insufficient cpu</code></p>

<p>The pod that you show (one of several) requests:</p>

<pre><code>cpu:     1
memory:  1000Mi
</code></pre>

<p>The cluster has insufficient capacity to deploy this pod (and apparently the others).</p>

<p>You should increase the number (and|or size) of the nodes in your cluster to accommodate the capacity needed for the pods.</p>

<p>You needn't delete these pods because, once the cluster's capacity increases, you should see these pods deploy successfully.</p>
