Provision Cloud Infrastructure with Gemini Reviews

WEI LIN S. · Reviewed over 1 year ago

Stone Y. · Reviewed over 1 year ago

Willie S. · Reviewed over 1 year ago

EW W. · Reviewed over 1 year ago

BHANU K. · Reviewed over 1 year ago

NARVEKAR S. · Reviewed over 1 year ago

Neelakanta K. · Reviewed over 1 year ago

Alekhya D. · Reviewed over 1 year ago

Chi Chien C. · Reviewed over 1 year ago

Jessica W. · Reviewed over 1 year ago

Aditi A. · Reviewed over 1 year ago

Bhavika .. · Reviewed over 1 year ago

YuLin S. · Reviewed over 1 year ago

Ken C. · Reviewed over 1 year ago

Dashmeen G. · Reviewed over 1 year ago

Chollangi J. · Reviewed over 1 year ago

benson l. · Reviewed over 1 year ago

Tzu Hua C. · Reviewed over 1 year ago

Akash C. · Reviewed over 1 year ago

open o. · Reviewed over 1 year ago

紹育 高. · Reviewed over 1 year ago

Hong-Yu L. · Reviewed over 1 year ago

Mark Chun W. · Reviewed over 1 year ago

Most of the commands provided by Gemini did not work as expected. Below is a summary of the Gemini commands, the issues faced, and the alternative commands used to complete the tasks successfully: Cluster Creation: Gemini Command: gcloud container clusters create gemini-demo --location=us-east1 --cluster-version=latest --enable-autopilot Issue: This command failed due to unspecified or incorrect parameters. Command Used Instead: gcloud container clusters create-auto gemini-demo --region us-east1 Note: The create-auto command worked successfully, setting up an Autopilot cluster in the specified region. Creating Deployment: Gemini Command: kubectl apply -f hello-server-deployment.yaml Issue: The command expected a specific YAML configuration file, which was either missing or not correctly set up. Command Used Instead: kubectl create deployment hello-server --image=us-docker.pkg.dev/google-samples/containers/gke/hello-app:1.0 Note: This command directly created the deployment using a specified container image. Exposing the Deployment: Gemini Command: kubectl expose deployment hello-server --type LoadBalancer --port 80 --target-port 8080 Issue: The command syntax was not properly recognized (missing equal signs for flags). Command Used Instead: kubectl expose deployment hello-server --type=LoadBalancer --port=80 --target-port=8080 Note: Adding the equal signs (=) after the flags resolved the issue. Retrieving Service Details: Gemini Command: kubectl get service hello-server -o jsonpath='{.status.loadBalancer.ingress[*].ip}' Issue: The command returned an error, possibly due to incorrect JSON path syntax or lack of ingress IP at the moment. Command Used Instead: kubectl get service hello-server Note: This simpler command provided the necessary service information, including the external IP, in a readable format. Summary: While Gemini provided commands that were close to achieving the desired tasks, many of them did not work as intended due to syntax errors, missing configuration files, or incorrect command parameters. The alternative commands used were simpler and successfully executed the required tasks.

Sunny D. · Reviewed over 1 year ago

Sikha N. · Reviewed over 1 year ago