Setting up a Private Kubernetes Cluster Reviews

Garima S. · Reviewed about 6 years ago

Ben C. · Reviewed about 6 years ago

Ben C. · Reviewed about 6 years ago

Ahmed a. · Reviewed about 6 years ago

It would help if the external address identified earlier on in the lab was better identified. Its use near the end is far enough along that it is all but forgotten.

Mike D. · Reviewed about 6 years ago

john s. · Reviewed about 6 years ago

The clusters couldn't be created. The command took more than 30 minutes but couldn't return.

Yau Tat L. · Reviewed about 6 years ago

NIKKI .. · Reviewed about 6 years ago

John M. · Reviewed about 6 years ago

DIego L. · Reviewed about 6 years ago

Olivier B. · Reviewed about 6 years ago

Sunil P. · Reviewed about 6 years ago

SAURAV K. · Reviewed about 6 years ago

Satish K. · Reviewed about 6 years ago

some typos in the lab, pls. review and fix them

Alexey S. · Reviewed about 6 years ago

One of the later instructions referred to using EXTERNAL_ADDRESS from previous output. Was a bit confusing as thought it referred to the output from the previous command rather than output from output a few steps earlier

Paolo R. · Reviewed about 6 years ago

Yu-Wei H. · Reviewed about 6 years ago

Learnt a lot here around the private cluster itself and the ability to access GCP APIs from a private subnet, but it was a bit repetitive. Would have been good to include a --num-nodes parameter in the create scripts to prevent accidentally going over resources allowances.

Kevin K. · Reviewed about 6 years ago

Sebastian B. · Reviewed about 6 years ago

ANTONIO F. · Reviewed about 6 years ago

In some steps I have added a parameter --zone us-central1-a becouse without it commands were not accepted

Dariusz B. · Reviewed about 6 years ago

Setting up a Private Kubernetes Cluster Completed

Zain B. · Reviewed about 6 years ago

MOHAMMAD a. · Reviewed about 6 years ago

.

Parikshit G. · Reviewed about 6 years ago