Mengamankan Google Kubernetes Engine dengan Cloud IAM dan Kebijakan Keamanan Pod Ulasan
12300 ulasan
Yes
Palteru S. · Diulas hampir 4 tahun lalu
Hayato M. · Diulas hampir 4 tahun lalu
Marko T. · Diulas hampir 4 tahun lalu
Olivier J. · Diulas hampir 4 tahun lalu
Shailesh K. · Diulas hampir 4 tahun lalu
David H. · Diulas hampir 4 tahun lalu
Guilherme d. · Diulas hampir 4 tahun lalu
Masatoshi F. · Diulas hampir 4 tahun lalu
Peik P. · Diulas hampir 4 tahun lalu
Vo X. · Diulas hampir 4 tahun lalu
Demian w. · Diulas hampir 4 tahun lalu
Kiril C. · Diulas hampir 4 tahun lalu
Eva R. · Diulas hampir 4 tahun lalu
Bernie B. · Diulas hampir 4 tahun lalu
Michael M. · Diulas hampir 4 tahun lalu
Niall W. · Diulas hampir 4 tahun lalu
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. · Diulas hampir 4 tahun lalu
Pongsak J. · Diulas hampir 4 tahun lalu
Leaf Y. · Diulas hampir 4 tahun lalu
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. · Diulas hampir 4 tahun lalu
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. · Diulas hampir 4 tahun lalu
Deepak S. · Diulas hampir 4 tahun lalu
The last part is confused
Sergio C. · Diulas hampir 4 tahun lalu
Brian D. · Diulas hampir 4 tahun lalu
Brian D. · Diulas hampir 4 tahun lalu
Kami tidak dapat memastikan bahwa ulasan yang dipublikasikan berasal dari konsumen yang telah membeli atau menggunakan produk terkait. Ulasan tidak diverifikasi oleh Google.