关于“Securing Google Kubernetes Engine with IAM and Pod Security Admission”的评价

SHREEKRISHNA B. · 评论over 1 year之前

Sarath T. · 评论over 1 year之前

Balaji G. · 评论over 1 year之前

Abdul Ashik Khan M. · 评论over 1 year之前

Raj G. · 评论over 1 year之前

Venkatreddy S. · 评论over 1 year之前

Zhengxian L. · 评论over 1 year之前

OK

Yerlan M. · 评论over 1 year之前

Yang L. · 评论over 1 year之前

Tamas N. · 评论over 1 year之前

Hisashi S. · 评论over 1 year之前

William Y. · 评论over 1 year之前

Julia M. · 评论over 1 year之前

Had a problem with the optional section. It wouldn't upgrade the default pool nodes at first, I was getting a 400 error about a cluster operation. Checked cluster status and there was 4th node listed in a paused-type state. Once cluster normalized and extra node disappeared, upgrade worked and completed credential rotation.

Allen B. · 评论over 1 year之前

Viviane G. · 评论over 1 year之前

CALEB H. · 评论over 1 year之前

Venkat A. · 评论over 1 year之前

Two issues: 1. Check progress for "Grant the Service Account User IAM Role to Username 2", doesn't work. I continued the lab, created the cluster etc (so the user obviously has permissions to carry on), and it still fails when checking progress. 2.monitoring logs - resource.type="k8s_cluster" protoPayload.response.reason="Forbidden" protoPayload.resourceName="core/v1/namespaces/restricted-ns/pods/nginx" You should state to press "show query" incase it is hidden. I had to manually search the error (By the end of it, I saw that there's a "show query" slide).

Ido G. · 评论over 1 year之前

done

Amol Z. · 评论over 1 year之前

Inspite of granting the service account user role to user 2, the stage does not succeed. If the role has not been granted, how can we go ahead and create the GKE cluster?

Balaji V. · 评论over 1 year之前

Arbaz Ahmed A. · 评论over 1 year之前

Amit S. · 评论over 1 year之前

Vishwanatha B. · 评论over 1 year之前

Alex P. · 评论over 1 year之前

Gowtham A. · 评论over 1 year之前