[root@qqmelo1c net.d]# oc get events
LAST SEEN FIRST SEEN COUNT NAME KIND SUBOBJECT TYPE REASON SOURCE MESSAGE
6h 10h 24 template-service-broker.158bdce32cfd10dd ClusterServiceBroker Normal FetchedCatalog service-catalog-controller-manager Successfully fetched catalog entries from broker.
6h 10h 127 ansible-service-broker.158bdce0550e223a ClusterServiceBroker Warning ErrorFetchingCatalog service-catalog-controller-manager Error getting broker catalog: Status: 404; ErrorMessage:
57m 57m 1 qqmelo1c.mylabserver.com.158bfb583b759511 Node Normal NodeHasSufficientPID kubelet, qqmelo1c.mylabserver.com Node qqmelo1c.mylabserver.com status is now: NodeHasSufficientPID
57m 57m 1 qqmelo1c.mylabserver.com.158bfb582e98163a Node Normal Starting kubelet, qqmelo1c.mylabserver.com Starting kubelet.
57m 57m 2 qqmelo1c.mylabserver.com.158bfb583b756e50 Node Normal NodeHasNoDiskPressure kubelet, qqmelo1c.mylabserver.com Node qqmelo1c.mylabserver.com status is now: NodeHasNoDiskPressure
57m 57m 2 qqmelo1c.mylabserver.com.158bfb583b74e6f2 Node Normal NodeHasSufficientDisk kubelet, qqmelo1c.mylabserver.com Node qqmelo1c.mylabserver.com status is now: NodeHasSufficientDisk
57m 57m 2 qqmelo1c.mylabserver.com.158bfb583b754883 Node
Y si queremos ver un log de un pod en particular, tiramos el comando siguiente
oc logs router-1-dmbx
No comments:
Post a Comment