Setting up a Private Kubernetes Cluster avis

Garima S. · Examiné il y a environ 6 ans

Ben C. · Examiné il y a environ 6 ans

Ben C. · Examiné il y a environ 6 ans

Ahmed a. · Examiné il y a environ 6 ans

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. · Examiné il y a environ 6 ans

john s. · Examiné il y a environ 6 ans

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

Yau Tat L. · Examiné il y a environ 6 ans

NIKKI .. · Examiné il y a environ 6 ans

John M. · Examiné il y a environ 6 ans

DIego L. · Examiné il y a environ 6 ans

Olivier B. · Examiné il y a environ 6 ans

Sunil P. · Examiné il y a environ 6 ans

SAURAV K. · Examiné il y a environ 6 ans

Satish K. · Examiné il y a environ 6 ans

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

Alexey S. · Examiné il y a environ 6 ans

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. · Examiné il y a environ 6 ans

Yu-Wei H. · Examiné il y a environ 6 ans

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. · Examiné il y a environ 6 ans

Sebastian B. · Examiné il y a environ 6 ans

ANTONIO F. · Examiné il y a environ 6 ans

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

Dariusz B. · Examiné il y a environ 6 ans

Setting up a Private Kubernetes Cluster Completed

Zain B. · Examiné il y a environ 6 ans

MOHAMMAD a. · Examiné il y a environ 6 ans

.

Parikshit G. · Examiné il y a environ 6 ans