Opinie (Navigate Security Decisions with Gemini)

Francisco B. · Sprawdzono prawie 2 lata temu

Krishan K. · Sprawdzono prawie 2 lata temu

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. · Sprawdzono prawie 2 lata temu

Wojciech S. · Sprawdzono prawie 2 lata temu

Utkarsh M. · Sprawdzono prawie 2 lata temu

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. · Sprawdzono prawie 2 lata temu

Raj U. · Sprawdzono prawie 2 lata temu

Swaleha K. · Sprawdzono prawie 2 lata temu

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

Steve G. · Sprawdzono prawie 2 lata temu

could not find Security / Edit Application layer Secrets Encryption checkbox

Steve G. · Sprawdzono prawie 2 lata temu

Reza R. · Sprawdzono prawie 2 lata temu

Chandrashekar B. · Sprawdzono prawie 2 lata temu

Kian Choon L. · Sprawdzono prawie 2 lata temu

some of the steps are not there

Ali K. · Sprawdzono prawie 2 lata temu

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. · Sprawdzono prawie 2 lata temu

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. · Sprawdzono prawie 2 lata temu

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

Yoel F. · Sprawdzono prawie 2 lata temu

Mohamadou C. · Sprawdzono prawie 2 lata temu

Shilpa M. · Sprawdzono prawie 2 lata temu

Fazmin S. · Sprawdzono prawie 2 lata temu

Kai H. · Sprawdzono prawie 2 lata temu

Vaibhav M. · Sprawdzono prawie 2 lata temu

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. · Sprawdzono prawie 2 lata temu

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.

Premkumar B. · Sprawdzono prawie 2 lata temu

Prathap R. · Sprawdzono prawie 2 lata temu