Configuring GKE-Native Monitoring and Logging Reviews

Didik S. · Reviewed about 5 years ago

Configuring Kubernetes Engine native Monitoring and Logging 5. In the Cloud Shell, execute the following command to verify the deployment exists. kubectl get deployments content_copy The output of this command will show that the hello-v2 application is running in the default namespace: NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE hello-v2 3 3 3 3 6s content_copy Click Check my progress to verify the objective. Configuring a GKE cluster with Kubernetes Engine Monitoring and deploy a sample workload Check my progress Please deploy a sample workload to your GKE cluster if already deployed wait till the log get created.

DON K. · Reviewed about 5 years ago

something seemed to go wrong with detecting the sample deployment.

Mark C. · Reviewed about 5 years ago

Lian K. · Reviewed about 5 years ago

Problem in the first validation

Edwin D. · Reviewed about 5 years ago

Yann C. · Reviewed about 5 years ago

Hua Tien Bernard K. · Reviewed about 5 years ago

Vivek S. · Reviewed about 5 years ago

sylvester S. · Reviewed about 5 years ago

Sergej K. · Reviewed about 5 years ago

Victor A. · Reviewed about 5 years ago

Nik G. · Reviewed about 5 years ago

Sergio G. · Reviewed about 5 years ago

Lovey T. · Reviewed about 5 years ago

Juliane B. · Reviewed about 5 years ago

Monitoring GKE and its logged data requires scalable metrics that can retrieve its GUI parameters in a browser

Anshuman M. · Reviewed about 5 years ago

Sergiusz R. · Reviewed about 5 years ago

Jonas V. · Reviewed about 5 years ago

Kevin F. · Reviewed about 5 years ago

Хисматуллин Р. · Reviewed about 5 years ago

Wong W. · Reviewed about 5 years ago

Anantha Rahul Reddy T. · Reviewed about 5 years ago

lab time needs to be extended by 30 mins

Sriram R. · Reviewed about 5 years ago

Sreeni G. · Reviewed about 5 years ago

Gaurav P. · Reviewed about 5 years ago