Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting our team. We will be in touch shortly.Close

  1. Blog
  2. Article

Hugo Huang
on 5 December 2023

Google Kubernetes Engine (GKE) traces its roots back to Google’s development of Borg in 2004, a Google internal system managing clusters and applications. In 2014, Google introduced Kubernetes, an open-source platform based on Borg’s principles, gaining rapid popularity for automating containerized application deployment. In 2015, Google launched GKE, a managed Kubernetes service on Google Cloud Platform (GCP), streamlining infrastructure management for users. Over the years, GKE saw substantial growth, introducing Autopilot mode in 2017 and surpassing 2 million managed clusters by 2019. Throughout 2020 and 2021, GKE continued evolving with features like Workload Identity and Anthos Config Management, aiding in access management and configurations. In 2022, GKE maintained its status as a leading managed Kubernetes platform, introducing innovations like Anthos Service Mesh and Anthos Multi-Cluster Ingress. GKE’s trajectory underscores the significance of containerization and cloud-native tech, poised to further empower the development, deployment, and management of modern applications amidst growing industry adoption.

Ubuntu can be used as the base operating system for GKE nodes, and GKE can be used to deploy and manage containerized applications on Ubuntu nodes.

Here are some of the benefits of using Ubuntu and GKE together:

  • Flexibility: Ubuntu can be used with a variety of Kubernetes distributions, so developing teams will have a standardized experience across multiple cloud, such as Azure Kubernetes Service (AKS) and Amazon EKS.
  • Secure. Timely updates and patches, building on Ubuntu’s security track record.
  • Stable. Long-term support with a consistent, predictable lifecycle and support commitment. Each GKE version has a customized version of Ubuntu that support its latest features.
  • Seamless. Developer-friendly, smooth experience from development to production.
  • Small. Ultra-small, resource-efficient, yet robust images with chiselled (distroless) Ubuntu.

Let’s go through the steps you need to deploy Ubuntu nodes in GKE.

  1. In Google Cloud Console, locate Kubernetes Engine:
  1. In “Clusters”, click CREATE:
  2. Choose “Standard: You manage your cluster” in the pop-up window:
  3. In the left of the console, click “default-pool”:
  4. Click “Nodes”:
  5. Find “Ubuntu with containerd (ubuntu_containerd)” in “Image type” drop-down menu:
  6. Choose “Ubuntu with containerd (ubuntu_containerd)” and Click “CREATE” at the bottom:
  7. Once the cluster is running, you can check “OS image” in the “Node details”:

Related posts

Serdar Vural
29 February 2024

Telco-grade Sylva-compliant Canonical platforms

Cloud and server Article

In December 2023, Canonical joined the Sylva project of Linux Foundation Europe to provide fully open-source and upstream telco platform solutions to the project. Sylva aims to tackle the fragmentation in telco cloud technologies and the vendor lock-in caused by proprietary platform solutions, by defining a common validation software fram ...

Serdar Vural
26 January 2024

Meet Canonical at Mobile World Congress Barcelona 2024

Ubuntu Article

The world’s largest and most influential telecommunications exhibition event, Mobile World Congress (MWC), is taking place in Barcelona on 26-29 February 2024. Canonical is excited to join this important annual event once again and meet the telecom industry.  Telecommunications is a key sector for Canonical. We offer solutions for private ...

Tytus Kurek
12 January 2024

Cloud-native infrastructure – When the future meets the present

Cloud and server Article

We’ve all heard about cloud-native applications in recent years, but what about cloud-native infrastructure? Is there any reason why the infrastructure couldn’t be cloud-native, too? Or maybe it’s already cloud-native, but you’ve never had a chance to dive deep into the stack to check it out? What does the term “cloud-native infrastructur ...