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

Julio L. · Reviewed over 5 years ago

Abhishek S. · Reviewed over 5 years ago

Mani R. · Reviewed over 5 years ago

Julio L. · Reviewed over 5 years ago

Harshith D. · Reviewed over 5 years ago

Mani R. · Reviewed over 5 years ago

Kevin F. · Reviewed over 5 years ago

Partha P. · Reviewed over 5 years ago

Jomon J. · Reviewed over 5 years ago

Lab contain not appropriately mentioned...

Partha P. · Reviewed over 5 years ago

Shubha B. · Reviewed over 5 years ago

luis E. · Reviewed over 5 years ago

Validation of last step didnt work

Miroslav J. · Reviewed over 5 years ago

S O. · Reviewed over 5 years ago

Jomon J. · Reviewed over 5 years ago

Jayaraj K. · Reviewed over 5 years ago

Not updated

Ankit D. · Reviewed over 5 years ago

Partha P. · Reviewed over 5 years ago

Andreas D. · Reviewed over 5 years ago

good

Abdul Kalam H. · Reviewed over 5 years ago

Miguel C. · Reviewed over 5 years ago

Quote: "Test the access of Username 2 2. You should now see that the option to create a cluster is now enabled. You may need to refresh the web browser tab for Username 2 to see the changes. " -> This is wrong. Username 2 has to logout and login again, to see the "Create" button enabled. Task: Grant the ServiceAccountUser IAM Role to Username 2 -> This task is not doable! Either the task description is completely bonkers, or Username 1 has not given the permission (setIAMPolicy) to add Username 2 as a ServiceAccountUser.

Gerhard K. · Reviewed over 5 years ago

There is some permission issue hence support team has raised a case. This is case No. #2132350 for this request. Also Lab is not very convenient

Partha P. · Reviewed over 5 years ago

Muhammad T. · Reviewed over 5 years ago

There is some permission issue hence support team has raised a case. This is case No. #2132350 for this request. Also Lab is not very convenient

Partha P. · Reviewed over 5 years ago