关于“AHYBRID021 Building Anthos Clusters on GCP and AWS”的评价
评论
error
Venkatareddy N. · 评论over 1 year之前
Anjali K. · 评论over 1 year之前
Muhammad A. · 评论over 1 year之前
Harshit K. · 评论over 1 year之前
vitas y. · 评论over 1 year之前
Rahul G. · 评论over 1 year之前
gg
Jit R. · 评论over 1 year之前
There was one problem. GKE cluster on us-central-1b region/zone failed creation with errors about resources unavailability. Due to that created GKE cluster on region us-west-1b. Also AWS Anthros / GKE creation has been more smoother and faster than GKE.
Ankush B. · 评论over 1 year之前
Yogesh S. · 评论over 1 year之前
OLEKSANDR S. · 评论over 1 year之前
ricardo c. · 评论over 1 year之前
Raghavendra B. · 评论over 1 year之前
Biswanath G. · 评论over 1 year之前
João P. · 评论over 1 year之前
Guillermo R. · 评论over 1 year之前
Nicolas Z. · 评论over 1 year之前
good
Vineeta N. · 评论over 1 year之前
Vijay C. · 评论over 1 year之前
good lab
Raghavendra B. · 评论over 1 year之前
The GKE cluster never creates bcs there is no resources in the region
Oriol B. · 评论over 1 year之前
Mohammad A. · 评论over 1 year之前
Maciej M. · 评论over 1 year之前
Emil C. · 评论over 1 year之前
Richard John R. · 评论over 1 year之前
Error at Step 4 when creating Anthos Cluster on AWS, although all previous steps have been performed : ERROR: (gcloud.container.aws.clusters.create) FAILED_PRECONDITION: could not get IAM instance profile: AccessDenied User: arn:aws:sts::785905340948:assumed-role/aws-cluster-anthos-api-role/multicloud-service-agent is not authorized to perform: iam:GetInstanceProfile on resource: instance profile aws-cluster-anthos-cp-instance-profile because no identity-based policy allows the iam:GetInstanceProfile action
Vanessa G. · 评论over 1 year之前
我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。