Connect and Manage Fleet Clusters
1. Connect and Manage Fleet Clusters
Next, let's explore how to create and manage clusters in a GKE fleet. Running GKE on VMware or bare metal is beyond the scope of this course. If you are interested in learning more, we recommend the one-day specialization courses. You can enable GKE fleets in the Google Cloud console by using gcloud commands in Cloud Shell or with Terraform. The first option is to use the Google Cloud console. First, navigate to the Google Kubernetes Engine page and then click Overview. Click Fleet Dashboard, then click Create a Fleet. When you enable fleets, a new fleet is created with the same name as your project and your clusters are automatically registered to it. You also have the option to manually configure fleet settings. To change the name of the fleet, enter the new name on the fleet registration page. To edit the cluster list, manually select which clusters to include in the fleet. Click Save. After you click Confirm, all required APIs and dependencies are enabled, the fleet is created, and specified clusters are registered to the fleet. You can also enable GKE fleets by using gcloud commands. First, run the gcloud services enable command to enable the GKE Hub API. If you haven't set a default project yet, specify your project ID. To create an empty fleet, run the gcloud container fleet create command, including the display name flag that defines the fleet name. As an alternative to gcloud commands, you can use Terraform to enable the GKE Hub API declaratively. To manage clusters in other public clouds, you'll need to enable specific Google Cloud Services by using the gcloud services enable command and the googleapis.com domain after each service-- gkemulticloud to support GKE clusters on multiple platforms; gkeconnect to establish connectivity between Google and managed clusters, both within Google and on-premises; connectgateway to securely connect external parties to GKE clusters; cloudresourcemanager to interact with Google Cloud metadata; and logging and monitoring to gain insight into your cluster's health and performance. This observability is extended with the opsconfigmonitoring and kubernetesmetadata APIs to offer more visibility into a multi-cluster environment. Now, when configuring GKE fleets, you'll need to make two key decisions. First is cluster location. Where will your Kubernetes clusters physically run? And second is the location of management services, like Policy Controller and Cloud Service Mesh. Where in Google Cloud will the core management services for your clusters reside? GKE fleets store your cluster's critical data, including resource information and encryption keys, in the Google Cloud region you specify. This allows you to meet specific data residency and compliance requirements. Google Cloud regions are associated with other cloud providers' regions for simplified management. For example, if you plan to run your cluster in AWS, but your data is located in Asia, you could choose the asia-southeast1 region in Google Cloud and the ap-southeast-1 region in AWS. More information on running clusters in other platforms is available in the reading materials for this module.2. Let's practice!
Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.