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

Ron S. · Reviewed over 3 years ago

Lesly G. · Reviewed over 3 years ago

Michael L. · Reviewed over 3 years ago

Richard N. · Reviewed over 3 years ago

Brayan G. · Reviewed over 3 years ago

Rony B. · Reviewed over 3 years ago

Ankur D. · Reviewed over 3 years ago

ok duuude!

0xc82e1ff0 S. · Reviewed over 3 years ago

siham s. · Reviewed over 3 years ago

Bobby K. · Reviewed over 3 years ago

‍이석민[ 정. · Reviewed over 3 years ago

User2 can't create cluster eventually. PodSecurityPolicies didn't work either. PodSecurityPolicies is to be deprecated by GKE and should be removed from the course.

Tianjun F. · Reviewed over 3 years ago

Bradley P. · Reviewed over 3 years ago

Inho K. · Reviewed over 3 years ago

Seokho S. · Reviewed over 3 years ago

정대 이. · Reviewed over 3 years ago

정대 이. · Reviewed over 3 years ago

Step "Grant the ServiceAccountUser IAM role to Username 2" is complete and can continue with the lab but will not give me credit for it. Now I have to document the step to prove I have credit. Luckily it didn't stop me from progressing since it's an early step of the lab.

Bradley P. · Reviewed over 3 years ago

박진홍 박. · Reviewed over 3 years ago

Min L. · Reviewed over 3 years ago

주영 G. · Reviewed over 3 years ago

might need to be reworked in the near time: Kubernetes has officially deprecated PodSecurityPolicy in version 1.21 and will be removed in 1.25 with no upgrade path available with this feature enabled.

Martin K. · Reviewed over 3 years ago

Min L. · Reviewed over 3 years ago

Baek D. · Reviewed over 3 years ago

최치영 최. · Reviewed over 3 years ago