GKE on AWS is hybrid cloud software that extends Google Kubernetes Engine (GKE) to Amazon Web Services (AWS). With GKE on AWS, you can create, manage, and upgrade GKE clusters in your AWS environment.
There are two components to GKE on AWS.
- Anthos management service, an environment that can install and update your user clusters.
- User clusters, GKE clusters where you run your workloads.
This topic describes the purpose and shape of your Anthos management service and user clusters.
The Anthos management service provides and manages components of your GKE on AWS installation. For example, you create Anthos GKE clusters using the management service. The management service provisions resources with the AWS API.
You need a management service in every AWS Virtual Private Cloud (VPC) where you run GKE on AWS. The management service is installed in one AWS Availability Zone. You only need one management service per VPC; a management service can manage multiple user clusters.
The primary component of the management service is the Cluster Operator. The Cluster Operator is a Kubernetes Operator that creates and manages your AWSClusters and AWSNodePools. The Cluster Operator stores configuration in an etcd database with storage persisted on an AWS EBS volume.
Installing and configuring your management service
This section describes the tools you can use to manage your management service.
The anthos-gke tool
With Connect, you can view and sign in to your GKE on AWS and GKE clusters on Google Cloud from the same interface in Google Cloud Console. All of your resources are shown in a single dashboard, so you can get visibility into your workloads across multiple Kubernetes clusters.
A user cluster includes two components, both of which are Kubernetes custom resources in the management service:
- A control plane for your GKE on AWS clusters.
- One or more AWSNodePools.
The default GKE on AWS installation creates an AWSCluster with three control plane replicas in the same availability zones. The management service places the control planes in a private subnet behind an AWS Network Load Balancer (NLB). The management service interacts with the control plane using NLB.
To create control planes across multiple AWS availability zones, see High availability user clusters.
Each control plane stores configuration in a local etcd database. These databases are replicated and set up in a stacked high availability topology.
One control plane manages one or more AWSNodePools.
AWSNodePools function like GKE Node Pools on Google Cloud. A node pool is a group of nodes within a cluster that all have the same configuration. Node pools use the AWSNodePool resource and can contain one or more nodes.
You can troubleshoot your GKE on AWS installation by viewing Kubernetes Events from your AWSCluster and AWSNodePools. For more information, see the Troubleshooting guide.