GKE Enterprise

A fleet is a logical grouping of Kubernetes clusters that can be managed collectively. GKE Enterprise capabilities are based on fleets, consisting entirely of GKE clusters hosted on Google Cloud or on-premises and on other public clouds like AWS and Azure.

Image source- Google Doc

You can enable the entire GKE Enterprise platform to use all available features, including multi-cloud and hybrid cloud capabilities, or you can create a fleet on Google Cloud only and pay for additional enterprise features as you need them. GKE Enterprise uses industry-standard open-source technologies and supports multiple infrastructure providers, providing flexibility to meet your business and organizational needs.

For information on the requirements for vSphere, see this document:

https://cloud.google.com/anthos/clusters/docs/on-prem/latest/how-to/vsphere-requirements

IP requirements

https://cloud.google.com/anthos/clusters/docs/on-prem/latest/how-to/plan-ip-addresses

Image Credit: Google

Your workloads run on user clusters

Deployment Steps: –

Details of my deployment environment: –

vSphere – 8.0

For my admin workstation, admin cluster, and user cluster deployment, I’m utilizing a single VLAN.

My IP details: –

Admin workstation – 172.16.0.42 —

— Admin Cluster —

Control VIP – 172.16.0.43

Control – 172.16.0.44

control2- 172.16.0.45

control3 – 172.16.0.46

— Workload/user cluster —

VIP – 172.16.0.47

control0- 172.16.0.48

control1- 172.16.0.49

control3- 172.16.0.50

worker0 – 172.16.0.51

wordker1- 172.16.0.52

wordker2- 172.16.0.53

worker-3- 172.16.0.54

ingress – 172.16.0.60

MetalLB Pool – 172.16.0.60-172.16.0.90

Deployment: –

On vSphere, create a Linux virtual machine. Ubuntu 22.04 VM is what I’m using.

You can clone my git repo https://github.com/Dineshk1205/gcp/tree/main or copy admin_worstation.sh

or copy admin_workstation.sh file to your machine.

The first five deployment stages (as mentioned above) will be completed by the admin_workstation.sh file.In the admin_workstation.sh file,

Give the necessary information for the admin workstation, vCenter, and GCP.

GCP Details: –

PROJECT_ID = project name you want to create in Google Cloud

GCP_ACCOUNT= your GCP account name

BILL_ACCOUNT_ID = GCP bill account ID (you can find it in the GCP portal)

vCenter Details: –

VCENTER_SERVER_ADDRESS= Your vCenter Address

VCENTER_USERNAME= vCenter Username

VCENTER_PASSWORD= vCenter Password

VCENTER_DC= vCenter Datacenter name, where you want to deploy a cluster admin workstation and clusters.

VCENTER_DATASTORE= vCenter Datastore name

VCENTER_CLUSTER= vCenter Cluster name

VCENTER_NETWORK=vCenter Network

VCENTER_FOLDER= vCenter Folder

VCENTER_RESOURCEPOOL= vCenter Resource Pool

Admin Workstation VM Details: –

ADMIN_WORKSTATION_IP= IP address for admin workstation VM

ADMIN_WORKSTATION_GATEWAY= gateway

ADMIN_WORKSTATION_NETMASK= netmask

ADMIN_WORKSTATION_DNS= dns server IP

NTP_SERVER= Ntp server

Save file.

Assign execute permission to the admin_workstation.sh script file.

$ chmod +x admin_workstation.sh

And run the script file

$ ./admin_workstation.sh

The y/n will be prompted. You can type n and enter.

Type Y and enter.

Following the installation of gcp cli, kubectl, and anthos-auth, a GCP login request will appear. Click the link in the browser and provide your GCP login information.

Accept permission after logging in, and code will appear. copy the code.

In the terminal, paste it.

The new project will be created and setup with the necessary API settings when the login process is finished.

The GCP console snapshot is seen below. Created the akubecluster project.

Once project, APi permission, service account created and gkeadm tool installed. vSphere configuration will be validated in the event that there are no errors. Adminworkstation VM will be created in the vSphere.

Adminworkstation has been successfully deployed.

You will notice the following files on the adminworkstation virtual machine.

Modify the admin-cluster.yaml file in accordance with your needs and environment.

Here is my file, admin-cluster. yaml. – https://github.com/Dineshk1205/gcp/blob/main/admin-cluster.yaml

Admin cluster configuration reference – https://cloud.google.com/anthos/clusters/docs/on-prem/latest/how-to/admin-cluster-configuration-file

after the preparation of admin-cluster.yaml.. Check configuration

$ gkectl check-config –config admin-cluster.yaml

Validation is going on .

The validation process was effectively finished.

Next, get the admin cluster ready.

$ gkectl prepare –config admin-cluster.yaml

The necessary templates will be downloaded and uploaded.

the admin cluster’s creation.

$ gkectl create admin –config admin-cluster.yaml

It can need a few minutes.

To see the cluster nodes’ current state, open a different terminal. In the adminworkstation virtual machine, kubeconfig will be generated.

The admin cluster deployment was successfully and connected to the gcp.

The admin cluster will be visible in the GCP Console.

To get further details, you must authenticate the cluster.

Assign required permission.

$ gcloud container fleet memberships generate-gateway-rbac \

–membership=clustername \

–role=clusterrole/cluster-admin \

–users=gcp account name \

–project=project name \

–kubeconfig=kubeconfig \

–context=clustername \

–apply

Authenticate the cluster via the GCP console.

You were able to view further cluster details when the authentication process was finished.

Deploying a User Cluster:-

Configure the user-cluster.yaml file in the adminwrokstation virtual machine (VM) in accordance with your needs.

The cluster file I use – https://github.com/Dineshk1205/gcp/blob/main/user-cluster.yaml

User cluster configuration reference – https://cloud.google.com/anthos/clusters/docs/on-prem/latest/how-to/user-cluster-configuration-file

A file called user-ipblock.yaml must also be created.

You can look at my user-ipblock.yaml file – https://github.com/Dineshk1205/gcp/blob/main/user-ipblock.yaml

as soon as the files user-cluster.yaml and user-ipblock.yaml were ready. To verify the setup, run the command below.

$ gkectl check-config –kubeconfig kubeconfig –config user-cluster.yaml

Lastly, run the command below to create the user cluster.

$ gkectl create cluster –kubeconfig kubeconfig –config user-cluster.yaml

The deployment of the user cluster was completed

Cluster attached to the GCP Console.

Authenticate cluster.

Similar to this, you may launch several user clusters according to your needs, and you can use the GCP console to administer each cluster.