Proteger o Google Kubernetes Engine com o Cloud IAM e políticas de segurança de pods avaliações

Julio L. · Revisado há over 5 years

Abhishek S. · Revisado há over 5 years

Mani R. · Revisado há over 5 years

Julio L. · Revisado há over 5 years

Harshith D. · Revisado há over 5 years

Mani R. · Revisado há over 5 years

Kevin F. · Revisado há over 5 years

Partha P. · Revisado há over 5 years

Jomon J. · Revisado há over 5 years

Lab contain not appropriately mentioned...

Partha P. · Revisado há over 5 years

Shubha B. · Revisado há over 5 years

luis E. · Revisado há over 5 years

Validation of last step didnt work

Miroslav J. · Revisado há over 5 years

S O. · Revisado há over 5 years

Jomon J. · Revisado há over 5 years

Jayaraj K. · Revisado há over 5 years

Not updated

Ankit D. · Revisado há over 5 years

Partha P. · Revisado há over 5 years

Andreas D. · Revisado há over 5 years

good

Abdul Kalam H. · Revisado há over 5 years

Miguel C. · Revisado há over 5 years

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. · Revisado há over 5 years

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. · Revisado há over 5 years

Muhammad T. · Revisado há over 5 years

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. · Revisado há over 5 years