Configuring GKE-Native Monitoring and Logging Reviews

Chi T. · Reviewed about 4 years ago

B J. · Reviewed about 4 years ago

Antonio N. · Reviewed about 4 years ago

PIZZATO F. · Reviewed about 4 years ago

The task 3 and task 4 questions are not clear. They seem to be out of order when naming alerts and policies.

Vic K. · Reviewed about 4 years ago

Suryanarayana M. · Reviewed about 4 years ago

Valeria G. · Reviewed about 4 years ago

Massimo Z. · Reviewed about 4 years ago

Rajesh S. · Reviewed about 4 years ago

Muhammad Yazid T. · Reviewed about 4 years ago

Gerard S. · Reviewed about 4 years ago

FERRARESE B. · Reviewed about 4 years ago

Tarun G. · Reviewed about 4 years ago

Tarun G. · Reviewed about 4 years ago

Tarun G. · Reviewed about 4 years ago

Eduard P. · Reviewed about 4 years ago

Nabendu B. · Reviewed about 4 years ago

Some warnings appeared: WARNING: The `--enable-stackdriver-kubernetes` flag is deprecated and will be removed in an upcoming release. Please use `--logging` and `--monitoring` instead. For more information, please read: https://cloud.google.com/stackdriver/docs/solutions/gke/installing. WARNING: Starting in January 2021, clusters will use the Regular release channel by default when `--cluster-version`, `--release-channel`, `--no-enable-autoupgrade`, and `--no-enable-autorepair` flags are not specified. WARNING: Starting with version 1.18, clusters will have shielded GKE nodes by default. WARNING: The Pod address range limits the maximum size of the cluster. Please refer to https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr to learn how to optimize IP address allocation. WARNING: Starting with version 1.19, newly created clusters and node-pools will have COS_CONTAINERD as the default node image when no image type is specified.

Петр Л. · Reviewed about 4 years ago

Keith D. · Reviewed about 4 years ago

maruthamuthu m. · Reviewed about 4 years ago

Good

Itish N. · Reviewed about 4 years ago

Diego Nicolas G. · Reviewed about 4 years ago

Steffen D. · Reviewed about 4 years ago

Had to do this Lab twice because task1 failed to mark as success on the first attempt.

Timo K. · Reviewed about 4 years ago

ZANGRANDI M. · Reviewed about 4 years ago