Using Role-based Access Control in Kubernetes Engine Reviews

Vít P. · Reviewed over 4 years ago

Vít P. · Reviewed over 4 years ago

Puteri A. · Reviewed over 4 years ago

Pavan Kumar R. · Reviewed over 4 years ago

Duncan D. · Reviewed over 4 years ago

ver slow lab

Leszek H. · Reviewed over 4 years ago

Luiz N. · Reviewed over 4 years ago

Ivan v. · Reviewed over 4 years ago

Edoardo C. · Reviewed over 4 years ago

Yogendra J. · Reviewed over 4 years ago

VARRESE M. · Reviewed over 4 years ago

Mohannad A. · Reviewed over 4 years ago

Vikas S. · Reviewed over 4 years ago

Naresh K. · Reviewed over 4 years ago

Pawel M. · Reviewed over 4 years ago

Lalo P. · Reviewed over 4 years ago

Onur B. · Reviewed over 4 years ago

Piotr G. · Reviewed over 4 years ago

Nombuso Sanelisiwe X. · Reviewed over 4 years ago

Aliaksei K. · Reviewed over 4 years ago

Toshiya S. · Reviewed over 4 years ago

Mitali S. · Reviewed over 4 years ago

RBAC was not explained in details. Just one scenario is not enough.

Atharv K. · Reviewed over 4 years ago

when ssh into auditor instance, first there's a question if we want to proceed, then creating the keys. then it asked "Did you mean zone [us-central1-a] for instance: [gke-tutorial-auditor] (Y/n)?" Answering 'n' seemed to confuse the system as it's the default zone: Error fetching possible zones for instance: [gke-tutorial-auditor]. ERROR: (gcloud.compute.ssh) Could not fetch resource: - Required 'compute.zones.list' permission for 'projects/qwiklabs-gcp-02-b0b2f0598d55'

Gustavo S. · Reviewed over 4 years ago

Gregor P. · Reviewed over 4 years ago