Navigate Security Decisions with Gemini Reviews

Ravikrishna Y. · Reviewed almost 2 years ago

Adam R. · Reviewed almost 2 years ago

Francisco B. · Reviewed almost 2 years ago

Krishan K. · Reviewed almost 2 years ago

On the 3rd run the GKE cluster was created but It had this error: Cluster test has unschedulable pods Problem Your cluster has 2 unschedulable pods Details Unschedulable pods recommendationservice-5846958db7-j74wx adservice-77c7c455b7-dclcj Also Genimi findings section was not present in the Security Findings. It looks like the Google cloud interface has changed and Lab instructions are not aligned with these changes.

Andrei M. · Reviewed almost 2 years ago

Wojciech S. · Reviewed almost 2 years ago

Utkarsh M. · Reviewed almost 2 years ago

instructions are clear and easy to follow, however for new learners of cyber security with no prior cloud infra knowledge will not understand whats going on. But its still a good experience.

lim J. · Reviewed almost 2 years ago

Raj U. · Reviewed almost 2 years ago

Swaleha K. · Reviewed almost 2 years ago

Don't really enjoy networking config but nice to know where things are and how to make changes

Steve G. · Reviewed almost 2 years ago

could not find Security / Edit Application layer Secrets Encryption checkbox

Steve G. · Reviewed almost 2 years ago

Reza R. · Reviewed almost 2 years ago

Chandrashekar B. · Reviewed almost 2 years ago

Kian Choon L. · Reviewed almost 2 years ago

some of the steps are not there

Ali K. · Reviewed almost 2 years ago

Later, second run for this lab. The cluster was not created in time and failed with the following error: Google Compute Engine: Not all instances running in IGM after 35m24.572943842s. Expected 1, running 0, transitioning 1. Current errors: [GCE_STOCKOUT]: Instance 'gke-test-default-pool-5829acff-svbf' creation failed: The zone 'projects/qwiklabs-gcp-03-b8ed4a79a3e3/zones/us-west1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later.

Andrei M. · Reviewed almost 2 years ago

The cluster was not created in time and failed with the following error: Google Compute Engine: Not all instances running in IGM after 35m15.491811565s. Expected 1, running 0, transitioning 1. Current errors: [GCE_STOCKOUT]: Instance 'gke-test-default-pool-b8822027-mr2j' creation failed: The zone 'projects/qwiklabs-gcp-04-75d5c98f7926/zones/us-west1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later.

Andrei M. · Reviewed almost 2 years ago

it takes too long to update the cluster and the lab cannot be finished. this is my second try

Yoel F. · Reviewed almost 2 years ago

Mohamadou C. · Reviewed almost 2 years ago

Shilpa M. · Reviewed almost 2 years ago

Fazmin S. · Reviewed almost 2 years ago

Kai H. · Reviewed almost 2 years ago

Vaibhav M. · Reviewed almost 2 years ago

There could be more clarity in the instructions. eg., This should take a few minutes _The above statement could have been highlighted_ After a couple minutes, _The above statement is an important message; could have been highlighted_ Click on the Cluster secrets encryption disabled finding. _The above statement could have been "Click on the "hyperlink" Cluster secrets encryption disabled finding." The default action of people if not told specifically, would be to click on the checkbox for the option and then wonder!!!._ The "Edit" option did not appear. Waiting for that to happen, the lab timed out. Wil try again... This time it took longer and didn't create "cluster test" in time Will try again. - Tried again. Got stuck in the "Creating cluster" part. The message said "This should take a few minutes" [How much is a few minutes we wondered? Waited many many minutes with the message "Creating cluster test in us-west1...working..." for a long long time. It must have been over 25 mins. We started wondering if it had time traveled to the wild west and got embroiled in a tussle with Jesse James or Billy the kid :-)] Lab ended timed out because of this. Trying again now. Completed lab session successfully, finally.

Premkumar B. · Reviewed almost 2 years ago