<p>I am trying to expose my applications running in my kubernetes cluster through AWS load balancer.
 I followed the document <a href="https://cloudyuga.guru/blog/cloud-controller-manager" rel="nofollow noreferrer">https://cloudyuga.guru/blog/cloud-controller-manager</a>   and got till the point where i added <code>--cloud-provider=external</code>  in <em>kubeadm.conf</em> file. 
But this document is based on Digitial Ocean cloud and i'm working on AWS, i'm confused if i have to run any deployment.yaml file to get the pods running which are in pending status if so please provide me the link, i'm stuck at this point.</p>

<pre><code>NAME                                                    READY   STATUS    RESTARTS   AGE
coredns-66bff467f8-dlx76                                0/1     Pending   0          3m32s
coredns-66bff467f8-svb6z                                0/1     Pending   0          3m32s
etcd-ip-172-31-74-144.ec2.internal                      1/1     Running   0          3m38s
kube-apiserver-ip-172-31-74-144.ec2.internal            1/1     Running   0          3m38s
kube-controller-manager-ip-172-31-74-144.ec2.internal   1/1     Running   0          3m37s
kube-proxy-rh8g4                                        1/1     Running   0          3m32s
kube-proxy-vsvlt                                        1/1     Running   0          3m28s
kube-scheduler-ip-172-31-74-144.ec2.internal            1/1     Running   0          3m37s
</code></pre>

hemanth_peddi
<p>The <code>coredns</code> pods are <code>pending</code> because you have not installed a Pod Network add-on yet. From the docs <a href="https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network" rel="nofollow noreferrer">here</a> you can choose any supported Pod Network add-on. For example to use calico</p>

<pre><code>kubectl apply -f https://docs.projectcalico.org/v3.14/manifests/calico.yaml
</code></pre>

<p>After the Pod Network add-on is installed the <code>coredns</code> pods should come up.</p>
