Opiniones sobre Cómo proteger Google Kubernetes Engine con Cloud IAM y políticas de seguridad de Pods

Yes

Palteru S. · Se revisó hace casi 4 años

Hayato M. · Se revisó hace casi 4 años

Marko T. · Se revisó hace casi 4 años

Olivier J. · Se revisó hace casi 4 años

Shailesh K. · Se revisó hace casi 4 años

David H. · Se revisó hace casi 4 años

Guilherme d. · Se revisó hace casi 4 años

Masatoshi F. · Se revisó hace casi 4 años

Peik P. · Se revisó hace casi 4 años

Vo X. · Se revisó hace casi 4 años

Demian w. · Se revisó hace casi 4 años

Kiril C. · Se revisó hace casi 4 años

Eva R. · Se revisó hace casi 4 años

Bernie B. · Se revisó hace casi 4 años

Michael M. · Se revisó hace casi 4 años

Niall W. · Se revisó hace casi 4 años

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. · Se revisó hace casi 4 años

Pongsak J. · Se revisó hace casi 4 años

Leaf Y. · Se revisó hace casi 4 años

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. · Se revisó hace casi 4 años

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. · Se revisó hace casi 4 años

Deepak S. · Se revisó hace casi 4 años

The last part is confused

Sergio C. · Se revisó hace casi 4 años

Brian D. · Se revisó hace casi 4 años

Brian D. · Se revisó hace casi 4 años