2 min read

Google recently announced that their Google Kubernetes Engine 1.10 is now generally available and is also ready for enterprise use.

For a prolonged time, enterprises have faced challenges such as security, networking, logging, and monitoring. With the availability of Kubernetes Engine 1.10, Google has introduced new and exciting features that have a built-in robust security for enterprise use, which are:

  • Shared Virtual Private Cloud (VPC): This enables better control of network resources
  • Regional Persistent Disks and Regional Clusters: These ensure higher-availability and stronger SLAs.
  • Node Auto-Repair GA and Custom Horizontal Pod Autoscaler: These can be used for greater automation.

New features in the Google Kubernetes Engine 1.10

Networking

One can deploy workloads in Google’s global Virtual Private Cloud (VPC) in a Shared VPC model. This gives you the flexibility to manage access to shared network resources using IAM permissions while still isolating departments.

Shared VPC lets organization administrators assign administrative responsibilities, such as creating and managing instances and clusters, to service project admins while maintaining centralized control over network resources like subnets, routers, and firewalls.


Shared VPC network in the Kubernetes engine 1.10

Storage

This will make it easy to build highly available solutions. The Kubernetes Engine will provide support for the new Regional Persistent Disk (Regional PD). Regional PD enables a persistent network-attached block storage with synchronous replication of data between two zones within a region.

One does not have to worry about application-level replication and can take advantage of replication at the storage layer, with the help of Regional PDs. This kind of replication offers a convenient building block using which one can implement highly available solutions on Kubernetes Engine.

Reliability

Regional clusters, which would be made available in some time soon, allow one to create a Kubernetes Engine cluster with a multi-master, highly-available control plane. This cluster would spread the masters across three zones in a region, which is an important feature for clusters with higher uptime requirements. Regional clusters also offer a zero-downtime upgrade experience when upgrading Kubernetes Engine masters.

The node auto-repair feature is now generally available. It monitors the health of the nodes in one’s cluster and repairs nodes that are unhealthy.

Auto-scaling

In Kubernetes Engine 1.10, Horizontal Pod Autoscaler supports three different custom metrics types in beta:

  • External – For scaling based on Cloud Pub/Sub queue length
  • Pods – For scaling based on the average number of open connections per pod
  • Object – For scaling based on Kafka running in the cluster

To know more about the features in detail, visit the Google Blog.

Read Next


Subscribe to the weekly Packt Hub newsletter. We'll send you the results of our AI Now Survey, featuring data and insights from across the tech landscape.

LEAVE A REPLY

Please enter your comment!
Please enter your name here