Securing Google Kubernetes Engine with Cloud IAM and Pod Security Policies Reviews

Yes

Palteru S. · Reviewed almost 4 years ago

Hayato M. · Reviewed almost 4 years ago

Marko T. · Reviewed almost 4 years ago

Olivier J. · Reviewed almost 4 years ago

Shailesh K. · Reviewed almost 4 years ago

David H. · Reviewed almost 4 years ago

Guilherme d. · Reviewed almost 4 years ago

Masatoshi F. · Reviewed almost 4 years ago

Peik P. · Reviewed almost 4 years ago

Vo X. · Reviewed almost 4 years ago

Demian w. · Reviewed almost 4 years ago

Kiril C. · Reviewed almost 4 years ago

Eva R. · Reviewed almost 4 years ago

Bernie B. · Reviewed almost 4 years ago

Michael M. · Reviewed almost 4 years ago

Niall W. · Reviewed almost 4 years ago

I rerun the lab and this time got all 100%. Problem is I did the same operations as before (when I received 83%) I think things that are difficult / impossible properly monitor or check, should not be used for grading

Robert D. · Reviewed almost 4 years ago

Pongsak J. · Reviewed almost 4 years ago

Leaf Y. · Reviewed almost 4 years ago

Lab is designed to spend 95% of time waiting for cluster operations. Last step failed to register even though everything went according to instructions.

Robert D. · Reviewed almost 4 years ago

student_01_9bb2786c8020@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-26139ce499b2)$ export UPGRADE_ID=$(gcloud container operations list --filter="operationType=UPGRADE_NODES and status=RUNNING" --format='value(name)') student_01_9bb2786c8020@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-26139ce499b2)$ gcloud container operations wait $UPGRADE_ID --zone=$my_zone ERROR: (gcloud.container.operations.wait) argument OPERATION_ID: Must be specified. Usage: gcloud container operations wait OPERATION_ID [optional flags] optional flags may be --help | --region | --zone For detailed information on this command and its flags, run: gcloud container operations wait --help student_01_9bb2786c8020@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-26139ce499b2)$ echo $UPGRADE_ID student_01_9bb2786c8020@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-26139ce499b2)$ export UPGRADE_ID=$(gcloud container operations list --filter="operationType=UPGRADE_NODES and status=RUNNING" --format='value(name)') student_01_9bb2786c8020@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-26139ce499b2)$ echo $UPGRADE_ID student_01_9bb2786c8020@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-26139ce499b2)$ gcloud container clusters update $my_cluster --zone $my_zone --complete-credential-rotation This will complete the in-progress Credential Rotation on cluster [standard-cluster-1]. The master will be updated to stop serving on the old IP address and only serve on the new IP address. Old cluster credentials will be invalidated. Make sure all API clients have been updated to communicate with the new IP address (e.g. by running `gcloud container clusters get-credentials --project qwiklabs-gcp-00-26139ce499b2 --zone us-central1-a standard-cluster-1`). If maintenence window is used, nodes are not recreated until a maintenance window occurs. See documentation https://cloud.google.com/kubernetes-engine/docs/how-to/credential-rotation on how to manually update nodes. This operation is long-running and will block other operations on the cluster (including delete) until it has run to completion. Do you want to continue (Y/n)? Y ERROR: (gcloud.container.clusters.update) ResponseError: code=400, message=Node pool "default-pool" requires recreation. student_01_9bb2786c8020@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-26139ce499b2)$ gcloud container clusters update $my_cluster --zone $my_zone --complete-credential-rotation This will complete the in-progress Credential Rotation on cluster [standard-cluster-1]. The master will be updated to stop serving on the old IP address and only serve on the new IP address. Old cluster credentials will be invalidated. Make sure all API clients have been updated to communicate with the new IP address (e.g. by running `gcloud container clusters get-credentials --project qwiklabs-gcp-00-26139ce499b2 --zone us-central1-a standard-cluster-1`). If maintenence window is used, nodes are not recreated until a maintenance window occurs. See documentation https://cloud.google.com/kubernetes-engine/docs/how-to/credential-rotation on how to manually update nodes. This operation is long-running and will block other operations on the cluster (including delete) until it has run to completion. Do you want to continue (Y/n)? Y ERROR: (gcloud.container.clusters.update) ResponseError: code=400, message=Node pool "default-pool" requires recreation. student_01_9bb2786c8020@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-26139ce499b2)$

SATTANATHAN P. · Reviewed almost 4 years ago

Deepak S. · Reviewed almost 4 years ago

The last part is confused

Sergio C. · Reviewed almost 4 years ago

Brian D. · Reviewed almost 4 years ago

Brian D. · Reviewed almost 4 years ago