

kubectl -n cattle-system logs -f rancher-784d94f59b-vgqzhĬert CN is “Kubernetes Ingress Controller Fake Certificate” Use kubectl and the pod name to list the logs from the pod. Normal Started 11m kubelet, localhost Started container Normal Created 11m kubelet, localhost Created container

Normal Pulled 11m kubelet, localhost Successfully pulled image "rancher/rancher:v2.0.4" Normal Pulling 11m kubelet, localhost pulling image "rancher/rancher:v2.0.4" Normal SuccessfulMountVolume 11m kubelet, localhost MountVolume.SetUp succeeded for volume "rancher-token-dj4mt" Normal Scheduled 11m default-scheduler Successfully assigned rancher-784d94f59b-vgqzh to localhost If the state is not Running, run a describe on the pod and check the Events. Use kubectl to check the cattle-system system namespace and see if the Rancher pods are in a Running state.
#AMAZON PHOTO DESKTOP APP WAITING STATUS HOW TO#
This section describes how to troubleshoot an installation of Rancher on a Kubernetes cluster.
