Linode Launches Managed Kubernetes Engine (LKE): What You Need to Know

Kubernetes

YOUR COSMETIC CARE STARTS HERE

Find the Best Cosmetic Hospitals

Trusted • Curated • Easy

Looking for the right place for a cosmetic procedure? Explore top cosmetic hospitals in one place and choose with confidence.

“Small steps lead to big changes — today is a perfect day to begin.”

Explore Cosmetic Hospitals Compare hospitals, services & options quickly.

✓ Shortlist providers • ✓ Review options • ✓ Take the next step with confidence

This article is based on reporting originally published by Container Journal on May 13, 2020.

Linode Kubernetes Engine Goes Generally Available

Linode announced the general availability of the Linode Kubernetes Engine (LKE), a fully managed Kubernetes service that provides teams with access to a Kubernetes control plane at no additional cost. The move positioned Linode as a cost-competitive alternative to larger cloud providers that charge separately for control plane management.

Howie Ross, Director of Engineering at Linode, stated that the company’s goal was to offer enterprise-grade Kubernetes cluster management at a price point not matched by the major cloud hyperscalers, where control plane access is frequently billed as a distinct, premium service.

Supported Kubernetes Versions and Regions at Launch

At general availability, LKE supported the following Kubernetes versions:

  • Kubernetes 1.17
  • Kubernetes 1.16
  • Kubernetes 1.15

Clusters were available in four data center regions at launch:

  • Dallas, TX
  • Fremont, CA
  • Newark, NJ
  • Sydney, Australia

Linode indicated plans to expand LKE availability to additional data centers based on customer demand.

What the LKE Control Plane Includes

The managed control plane exposed through LKE comes with a meaningful set of built-in capabilities, reducing the operational overhead typically associated with self-managed Kubernetes deployments:

  • Linode Cloud Controller Manager – Automates Kubernetes version upgrades and provides backup and recovery tooling.
  • Kubernetes API server – Standard API access for cluster management and automation.
  • Scheduler – Manages workload placement across nodes.
  • etcd – The open-source distributed key/value store used for cluster state persistence.
  • Resource controllers – Standard Kubernetes controllers for managing deployments, replica sets, and other resources.

Storage and Networking Integration

LKE ships with production-ready integrations for both storage and networking:

  • Linode Container Storage Interface (CSI) driver – Enables dynamic provisioning and management of Linode block storage volumes directly from within Kubernetes workloads.
  • NodeBalancer integration – Allows teams to provision and configure Linode’s load balancers automatically through Kubernetes Service objects of type LoadBalancer.

Third-Party Tooling Support

LKE launched with integrations for widely adopted DevOps and infrastructure tools:

  • Helm – For Kubernetes package management and application templating.
  • Terraform – For infrastructure-as-code provisioning of LKE clusters and associated resources.
  • Rancher Labs – For teams that prefer Rancher’s multi-cluster management interface on top of LKE.

Why Managed Kubernetes Matters for DevOps Teams

Running Kubernetes in production involves considerably more than standing up a cluster. Teams must manage the control plane, handle upgrades, configure networking and storage integrations, and maintain observability and backup pipelines. For many organizations, this operational burden is a barrier to adoption.

Managed services like LKE offload control plane responsibilities to the provider, allowing engineering teams to focus on application delivery rather than cluster operations. Ross highlighted that LKE was designed to allow teams to deploy applications on Kubernetes with minimal setup friction.

The cost angle is also significant: providers like AWS, Google Cloud, and Azure have historically charged for managed control plane access (for example, Amazon EKS charges a per-cluster fee). Linode’s decision to include the control plane at no extra cost directly targets cost-sensitive teams and smaller organizations running Kubernetes workloads.

The Broader Kubernetes Adoption Context

The LKE launch came during a period of growing interest in container orchestration, with organizations increasingly recognizing Kubernetes as the de facto standard for running scalable, resilient applications. At the same time, self-managed Kubernetes deployments remain complex and resource-intensive, creating demand for managed offerings that reduce operational overhead without sacrificing flexibility.

Kubernetes’ ability to scale infrastructure up and down on demand also made it particularly relevant for organizations reassessing their application architecture for resilience and agility.

Summary

FeatureLKE at GA (May 2020)
Kubernetes versions1.15, 1.16, 1.17
Control plane costIncluded (no extra charge)
RegionsDallas, Fremont, Newark, Sydney
StorageLinode CSI driver (block storage)
Load balancingNodeBalancer integration
IaC supportTerraform
Package managementHelm
Multi-cluster UIRancher Labs integration

Note: LKE features, supported Kubernetes versions, pricing, and regional availability have likely changed since this original announcement in May 2020. Refer to Linode’s official LKE documentation for current details.

0 0 votes
Article Rating
Subscribe
Notify of
guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x