I follow the following blog to create a Kubernetes cluster (on AWS EC2).
I have finished executing the commands until the master configuration. However, the Dashboard and Calico network depend on the status. Googled and found many resources that are not useful in my case, for example: Some problems were due to the unavailability of the scheduler. Here I have it. And I am very sure that I have necessarily done all these steps one after the other. Here is the result:
kubectl gets pods -o wide -all-namespaces
NAMESPACE NAME READY STATUS RESTARTS OLD IP-NODE NOMINATED NODE-READINESS-GATES
kube-system calico-kube-controller-694687c474-r55p7 0/1 Pending 0 18m
kube system coredns-86c58d9df4-25fxt 0/1 Pending 0 33m
kube system coredns-86c58d9df4-w6mfx 0/1 Pending 0 33m
kube system etcd-kmaster 1/1 running 0 37m 172.31.40.185 kmaster
kube-system kube-apiserver-kmaster 1/1 Running 0 37m 172.31.40.185 kmaster
kube-system kube-controller-manager-kmaster 1/1 Running 0 37m 172.31.40.185 kmaster
kube-system kube-proxy-l4wr6 1/1 running 0 38m 172.31.40.185 kmaster
kube-system kube-scheduler-kmaster 1/1 Running 0 37m 172.31.40.185 kmaster
kube system kubernetes-dashboard-57df4db6b-s7pzt 0/1 Pending 16m
As you can see, it has been in Calico and Kube Dashboard status for more than 15 minutes. All other solutions / ideas would be really grateful.