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

Julio L. · Reviewed больше 5 лет ago

Abhishek S. · Reviewed больше 5 лет ago

Mani R. · Reviewed больше 5 лет ago

Julio L. · Reviewed больше 5 лет ago

Harshith D. · Reviewed больше 5 лет ago

Mani R. · Reviewed больше 5 лет ago

Kevin F. · Reviewed больше 5 лет ago

Partha P. · Reviewed больше 5 лет ago

Jomon J. · Reviewed больше 5 лет ago

Lab contain not appropriately mentioned...

Partha P. · Reviewed больше 5 лет ago

Shubha B. · Reviewed больше 5 лет ago

luis E. · Reviewed больше 5 лет ago

Validation of last step didnt work

Miroslav J. · Reviewed больше 5 лет ago

S O. · Reviewed больше 5 лет ago

Jomon J. · Reviewed больше 5 лет ago

Jayaraj K. · Reviewed больше 5 лет ago

Not updated

Ankit D. · Reviewed больше 5 лет ago

Partha P. · Reviewed больше 5 лет ago

Andreas D. · Reviewed больше 5 лет ago

good

Abdul Kalam H. · Reviewed больше 5 лет ago

Miguel C. · Reviewed больше 5 лет 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 больше 5 лет 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 больше 5 лет ago

Muhammad T. · Reviewed больше 5 лет 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 больше 5 лет ago