Implement continuous delivery with Gemini avis

Vinay Reddy G. · Examiné il y a presque 2 ans

This session failed to create GKE Clusters

GCP S. · Examiné il y a presque 2 ans

Truong Q. · Examiné il y a presque 2 ans

Francisco B. · Examiné il y a presque 2 ans

Ravikrishna Y. · Examiné il y a presque 2 ans

Prathap R. · Examiné il y a presque 2 ans

Raj U. · Examiné il y a presque 2 ans

Reza R. · Examiné il y a presque 2 ans

Telaprolu Krishna K. · Examiné il y a presque 2 ans

Fazmin S. · Examiné il y a presque 2 ans

cut off

Ali K. · Examiné il y a presque 2 ans

Outstanding. I'll never parse a log file again!

Jeff M. · Examiné il y a presque 2 ans

Marvin N. · Examiné il y a presque 2 ans

Mohamadou C. · Examiné il y a presque 2 ans

Praveen Babu T. · Examiné il y a presque 2 ans

Shilpa M. · Examiné il y a presque 2 ans

Vaibhav M. · Examiné il y a presque 2 ans

Maja R. · Examiné il y a presque 2 ans

The same issue in this lab too, in creating the cluster. "Creating cluster test" goes on indefinitely. Since, it was taking an unusually long time to create the cluster, I decided to ask Gemini why. Here is the command and the response. P: Why is it that the command "gcloud container clusters create" taking an unusually long time to create a cluster? I got this elaborate Reply: There are a few reasons why the gcloud container clusters create command might be taking an unusually long time to create a cluster. High demand . GKE is a popular service, and there may be a high demand for clusters at the moment. This can lead to longer wait times for cluster creation. Large cluster . If you are creating a large cluster, it will take longer to create than a small cluster. This is because GKE has to provision more resources for a large cluster. Custom configuration . If you are creating a cluster with a custom configuration, such as a custom node pool or a custom network, it will take longer to create than a cluster with a default configuration. This is because GKE has to do more work to set up the custom configuration. Network issues . If there are any network issues between your computer and the GKE API, this can slow down the cluster creation process. Other issues . There may be other issues that are causing the cluster creation process to take a long time. These issues could be related to your project, your cluster, or the GKE service itself. If you are experiencing an unusually long wait time for cluster creation, you can try the following: Check the GKE status page . The GKE status page provides information about any known issues that may be affecting the service. Contact Google Cloud support . If you are unable to resolve the issue on your own, you can contact Google Cloud support for help. Here are some additional tips that may help to reduce the time it takes to create a cluster: Use a default configuration . If you do not need to customize your cluster, use the default configuration. This will help to speed up the cluster creation process. Create a smaller cluster . If you do not need a large cluster, create a smaller cluster. This will also help to speed up the cluster creation process. Avoid creating clusters during peak hours . If possible, avoid creating clusters during peak hours. This will help to reduce the chances of experiencing a long wait time. Our thoughts: I discounted the options one by one; probably not High demand, it is not a large cluster, it isn't custom config, there doesn't seem to be network issues. I thought I will check the GKE status page. So, I asked "How do I access the GKE status page?" The reply was, You can access the GKE status page at the following URL: https://status.cloud.google.com/incidents?component=container.googleapis.com The GKE status page provides information about the current status of the GKE service, as well as any known issues that may be affecting the service. You can also subscribe to the GKE status page to receive email notifications about any new incidents or updates. To subscribe, click on the "Subscribe to updates" button on the status page. Clicking on the link produced a 404 error. So, I told Gemini so. It apologized, but shared the same link. It again shared the same link, but with an explanation "If you are still getting a 404 error, it is possible that there is a problem with your internet connection or that the GKE status page is temporarily unavailable. You can try refreshing the page or checking back later." I responded so: "the Internet is fine. other Internet links are accessible. Escalate this" The response to this was, I understand that you are still getting a 404 error when trying to access the GKE status page. I have escalated this issue to the Google Cloud team, and they are currently investigating the problem. In the meantime, you can check the status of GKE in your project by running the following command: gcloud container clusters list So, What I did was, Open a new terminal tab and entered the command gcloud container clusters list The response was NAME: test LOCATION: us-west1-b MASTER_VERSION: 1.28.7-gke.1026000 MASTER_IP: 35.203.141.190 MACHINE_TYPE: e2-standard-4 NODE_VERSION: 1.28.7-gke.1026000 NUM_NODES: 3 STATUS: PROVISIONING So, I understand that the process is getting stuck somewhere. I decide to end the lab and restart it. - This time, it took about 8 minutes to create the cluster test. I timed it. I conclude that if it takes more than 10 minutes to create the cluster, you could end the lab and restart it, to save time. I would suggest that you make this statement as part of the instructions, to help students. *Lab successfully completed*

Premkumar B. · Examiné il y a presque 2 ans

Shweta V. · Examiné il y a presque 2 ans

Kisho I. · Examiné il y a presque 2 ans

Sunil K. · Examiné il y a presque 2 ans

Jack U. · Examiné il y a presque 2 ans

Great

Jayesh M. · Examiné il y a presque 2 ans

sourabh s. · Examiné il y a presque 2 ans