Reading time ~3 minutes
A Quick Look at GKE Autopilot (in 15 minutes)
This week Google introduced GKE Autopilot, defined as a fully managed, hardened Kubernetes cluster out of the box, for true hands-free operations.
I was curious to take a look at it, so if you don’t have time to play with it, I did it for you.
Setup from Scratch
Here is a step-by-step walkthrough on how to get a GKE Autopilot running starting from a new (empty) GCP Project:
|Enable the GKE APIs|
|Go to the GKE Console and create a cluster|
|Choose a name, region, and
|In the Networking settings, tick “Access control plane using its external IP address”. I selected this for easiness, but you can look at “Creating a private cluster” in the docs for a fully private cluster|
|After a few minutes (~5), the cluster will be ready|
With the cluster up and running, let’s start by taking a look at the security defaults.
From the networking point of view, it can be seen that the control plane can be accessed via a public IP address (“Control plane address range”), alongside the pod and service address ranges. It is worth noting also how control plane authorized networks and network policies are set as disabled.
At the same time, the main dashboard provides a handy view over general cluster and Autoscaler’s logs.
Subscribe to CloudSecList
Connecting to the Cluster
Two options are available, either by checking workloads in the dashboard or via command line:
Connecting to the cluster via Cloud Shell resulted to be super quick:
One of the main advantages of Autopilot is exactly that it allows customers to focus on workloads rather than on managing the cluster itself.
This reflects also in the number of steps required to deploy a simple “hello world”.
We can also validate the status of the deployment via Cloud Shell:
This post described my first interaction with GKE Autopilot, so that if you don’t have time to play with it, I did it for you.
Overall, it does provide a streamlined and quick experience to get from zero to a “hello world” service fully deployed. What I’ll be interested next is to explore the security implications of this setup.
I hope you found this post useful and interesting, and I’m keen to get feedback on it! If you find the information shared was useful, if something is missing, or if you have ideas on how to improve it, please let me know on Twitter.