关于“Securing Google Kubernetes Engine with Cloud IAM and Pod Security Policies”的评价

time should have been provided atleast for 2 hrs. insufficient time.

Nazia B. · 已于 over 4 years前审核

Arnab D. · 已于 over 4 years前审核

Cesar G. · 已于 over 4 years前审核

Domenico B. · 已于 over 4 years前审核

Wojciech P. · 已于 over 4 years前审核

Stephen A. · 已于 over 4 years前审核

Alexandre R. · 已于 over 4 years前审核

Muhammad S. · 已于 over 4 years前审核

Yuya S. · 已于 over 4 years前审核

arindam c. · 已于 over 4 years前审核

Carlos C. · 已于 over 4 years前审核

Thanks a lot

Alonso P. · 已于 over 4 years前审核

Isaac Y. · 已于 over 4 years前审核

Орловский А. · 已于 over 4 years前审核

Tomasz K. · 已于 over 4 years前审核

Nagendra V. · 已于 over 4 years前审核

Toby S. · 已于 over 4 years前审核

- in the exercise it says to choose Kubernetes Engine Developer, but at the check it requests for Kubernetes Engine Admin - even after I created the CLusterRoleBinding, still the user 2 was not able to create unprivileged pod, even if I restarted the google cloud portal session

Mihai D. · 已于 over 4 years前审核

Didn't have enough time to actually complete the credential rotation. There were quite a few of time consuming operations.

Constantin A. · 已于 over 4 years前审核

Alin C. · 已于 over 4 years前审核

:0

Beatriz Adriana O. · 已于 over 4 years前审核

Jakub K. · 已于 over 4 years前审核

Wojciech P. · 已于 over 4 years前审核

Robert B. · 已于 over 4 years前审核

Wojciech P. · 已于 over 4 years前审核