Setting up a Private Kubernetes Cluster Reviews

lab gives me not existing zone us-west8-c

Şaban U. · Reviewed около 2 месяцев ago

Francis M. · Reviewed около 2 месяцев ago

Fatma M. · Reviewed около 2 месяцев ago

Pratik B. · Reviewed около 2 месяцев ago

Krish M. · Reviewed около 2 месяцев ago

Marek G. · Reviewed около 2 месяцев ago

MADHAVI A. · Reviewed около 2 месяцев ago

Ludvig H. · Reviewed около 2 месяцев ago

Brian W. · Reviewed около 2 месяцев ago

Kelly V. · Reviewed около 2 месяцев ago

Siva K. · Reviewed около 2 месяцев ago

Atsushi A. · Reviewed около 2 месяцев ago

I did it pretty much twice and it always failed on both times it asked to run these commands: kubectl get nodes --output yaml | grep -A4 addresses kubectl get nodes --output wide Here is a sample of the error messages: E0616 21:48:18.569175 2752 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"https://34.177.109.167/api?timeout=32s\": dial tcp 34.177.109.167:443: i/o timeout"

Hilton P. · Reviewed около 2 месяцев ago

Jorge Yezid M. · Reviewed около 2 месяцев ago

Eduardo M. · Reviewed около 2 месяцев ago

Najet B. · Reviewed около 2 месяцев ago

Ercasul C. · Reviewed около 2 месяцев ago

Asko K. · Reviewed около 2 месяцев ago

Silvia F. · Reviewed около 2 месяцев ago

Moa T. · Reviewed около 2 месяцев ago

Francesco V. · Reviewed около 2 месяцев ago

very poor. i am trying the whole lap to access the vm of source instance and it refuses and saying permission denied because the public key and i think the problem is state/key mismatch issues inside Cloud Shell + OS Login propagation very unsatisfied

anass e. · Reviewed около 2 месяцев ago

Iqbaal R. · Reviewed около 2 месяцев ago

John Ross M. · Reviewed около 2 месяцев ago

Manish J. · Reviewed около 2 месяцев ago