关于“Installing and Managing Apigee Hybrid”的评价

student_00_6529a59a4487@cloudshell:~/apigee/hybrid-files (qwiklabs-gcp-03-a1778f6e58ad)$ $APIGEECTL_HOME/apigeectl init -f overrides/overrides-test.yaml Parsing file: config/values.yaml Parsing file: overrides/overrides-test.yaml E0628 07:20:40.718246 3861 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request E0628 07:20:41.163747 3861 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request error: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request

Lam B. · 评论over 2 years之前

Ankur J. · 评论over 2 years之前

good

Aoushagoni A. · 评论over 2 years之前

Vivek S. · 评论over 2 years之前

Cédric G. · 评论over 2 years之前

Elbert D. · 评论over 2 years之前

Sriraksha N. · 评论over 2 years之前

Eduardo R. · 评论over 2 years之前

step 7, can not completed: Too many levels of symbolic links

Eduardo R. · 评论over 2 years之前

Prajakta S. · 评论over 2 years之前

Huiling P. · 评论over 2 years之前

Danny M. · 评论over 2 years之前

Bondhan N. · 评论over 2 years之前

I just couldn't go past check-ready step. It fails with apigee-controller-manager is not running.

Ayele A. · 评论over 2 years之前

Tonatiuh M. · 评论over 2 years之前

Abhishek A. · 评论over 2 years之前

Alessandro P. · 评论over 2 years之前

Carlo Alberto L. · 评论over 2 years之前

Stefano V. · 评论over 2 years之前

Davide G. · 评论over 2 years之前

Alessandro M. · 评论over 2 years之前

Antonino C. · 评论over 2 years之前

Harshitha B. · 评论over 2 years之前

Jhon R. · 评论over 2 years之前

Received the below error message and couldn't recover student_03_525f7ef6b781@cloudshell:~/apigee/hybrid-files (qwiklabs-gcp-03-9dcaf96f5c36)$ $APIGEECTL_HOME/apigeectl init -f overrides/overrides-test.yaml --dry-run=client Parsing file: config/values.yaml Parsing file: overrides/overrides-test.yaml E0607 21:50:26.242697 3945 memcache.go:265] couldn't get current server API group list: Get "https://34.170.146.133/api?timeout=32s": dial tcp 34.170.146.133:443: i/o timeout Unable to connect to the server: dial tcp 34.170.146.133:443: i/o timeout

Raymond L. · 评论over 2 years之前