Author: examcert

To delete a GKE cluster, we need to use the following command:gcloud container clusters delete CLUSTER_NAME –-zone=zone_name In the next screenshot, we see the progress and output of the command that leads to cluster deletion: Figure 6.13 – Cluster deletion using CLI By performing cluster operations, we have delved deeper into GKE management. Let’s move…

The procedure doesn’t differ from the Cloud console procedure. The step we didn’t have in Cloud console is retrieving available versions. Proceed as follows: This results in the following output: Figure 6.8 – Available GKE versions from different release channels This results in the following output: Figure 6.9 – Command to upgrade the GKE cluster…

To list GKE clusters in use, we can use the gcloud container clusters list command in either Cloud Shell or your local computer, resulting in the following output: Figure 6.4 – Output of the gcloud container clusters list command with clusters listed To drill down into a specific cluster, we can use the following command:gcloud…

The second part of the chapter about implementing compute solutions using Google Kubernetes Engine (GKE) focuses on operations such as cluster, node pool, Pod, and Service management. The following topics are covered: In the previous chapter about GKE, we learned how to create clusters in Standard and Autopilot modes. In this chapter, we will focus…

The beauty of Kubernetes is that applications developed, tested, and run on-premises can be moved to other Kubernetes environments without major refactoring. Of course, if you use a specific load balancer or storage type that isn’t available in GKE, you will need to adjust those settings. In the next section, we will learn what Artifact…

We already know what differentiates GKE Standard and Autopilot, and we will focus on GKE deployment in Autopilot mode. Cloud Console Similar to standard GKE deployment, we need to click the Create button to start. As you will see in the screenshots and overall deployment flow, the deployment is much more simplified than with Standard…

As with any other service in Google Cloud, the Kubernetes Engine API must be enabled before using the service. Once the API is enabled, we can proceed with our Kubernetes cluster creation. As mentioned, a GKE deployment can be created with two modes—Autopilot and Standard. We will choose the Standard mode, but we encourage you…

Cloud Shell and its gcloud set of commands can be used to manage GKE together with Cloud Console. The gcloud command can be handy when you want to script and automate GKE-related tasks. Cloud SDK Cloud SDK provides Cloud Client Libraries, allowing you to interact with GKE resources. SDK libraries are available in the following…

Autopilot is a relatively new product from Google Cloud—it was released in February 2021. Following this announcement, GKE now offers two modes of usage: Standard and Autopilot. We just discussed Standard mode, where we can configure multiple GKE options and fine-tune it to our liking. Autopilot mode, however, aims at delivering industry best practices and…

As with a pure Kubernetes architecture, a cluster is the foundation of GKE. GKE clusters consist of one or more control planes and multiple worker machines where the workload runs, called nodes. The control plane and nodes are the main components of the container orchestration system: Figure 5.4 – GKE standard architecture Control plane The…