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

Jesús Alberto D. · Revisado há over 4 years

Keshaw K. · Revisado há over 4 years

Jongwon L. · Revisado há over 4 years

Diana P. · Revisado há over 4 years

proxy m. · Revisado há over 4 years

RE-tried, got "no permission" again "You need permissions for this action. Required permission(s): iam.serviceAccounts.setIamPolicy" Re-tried, the error below was fixed, but encountered another Permission error! kubectl apply -f restricted-psp.yaml Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+ Error from server (Forbidden): error when creating "restricted-psp.yaml": podsecuritypolicies.policy is forbidden: User "student-00-61c1f16ae4e8@qwiklabs.net" cannot create resource "podsecuritypolicies" in API group "policy" at the cluster scope: requires one of ["container.podSecurityPolicies.create"] permission(s). ========== This is the worst lab I have tried in Google cloud. The support should go to check the log! There is the blocker in lab "Securing Google Kubernetes Engine with Cloud IAM and Pod Security Policies", section "Grant the ServiceAccountUser IAM Role to Username 2" step 4 - Click the Manage access button on the screen to open the permissions information panel. The permissions information panel will open on the right side of the window. ". Whn i click on the Manage access button I got no permission message, here is the message - "You need permissions for this action. Required permission(s): iam.serviceAccounts.setIamPolicy". It seems the user1 "student-00-e04e462eebfb@qwiklabs.net doesn't have iam.serviceAccounts.setIamPolicy permission. The lab missed granted user1 the permission. This is my second time try. Please have a look at that issues. Thanks.

Rose C. · Revisado há over 4 years

Ruben L. · Revisado há over 4 years

ok

Veeraram M. · Revisado há over 4 years

Jesús Alberto D. · Revisado há over 4 years

Kevin A. · Revisado há over 4 years

Vladislav Z. · Revisado há over 4 years

Damiano V. · Revisado há over 4 years

BALZANO F. · Revisado há over 4 years

Andrei B. · Revisado há over 4 years

Ashish T. · Revisado há over 4 years

both user did not have permission on IAM

Kumar Amit (. · Revisado há over 4 years

Not working at 2nd attempt.

Razvan-Dumitru T. · Revisado há over 4 years

Mihai I. · Revisado há over 4 years

Mihai S. · Revisado há over 4 years

Cristian N. · Revisado há over 4 years

Cristian N. · Revisado há over 4 years

Maria C. · Revisado há over 4 years

Anca-Maria R. · Revisado há over 4 years

The cluster upgrades took a very long time.

Razvan-Dumitru T. · Revisado há over 4 years

A bit to the limit, buffer time could be increased.

Tudor M. · Revisado há over 4 years