With Kubernetes 1.7, Container Engine is adding a number of new security enhancements including the Node authorizer, the Kubernetes NetworkPolicy API, and HTTP re-encryption.

Google said in the blog post about the release of 1.10: Kubernetes Engine, the first production-grade managed Kubernetes service, has been generally available since 2015.

Correction: I originally misnamed Google Kubernetes Engine as Google Container Services. It was rebranded from Google Container Engine at the end of 2017, but I still managed to mix it up somehow.

Overall, the Kubernetes Engine (which seems to be Google’s preferred nom du guerre for the GKE now) saw its core-hours grow 9x year over year in 2017.

KEDA is an autoscaling engine designed to extend the default feature set of Kubernetes. In particular, it’s built to help applications that run on the container orchestration platform more ...

Unsurprisingly, that often means adding support for containers, which is exactly what Linode is doing with the beta launch of its Linode Kubernetes Engine (LKE) this week.

Maximizing utilization Kubernetes clusters, a group of nodes running containerized apps, are often less than 30% utilized, according to Maskasky. With EMP, Platform9 looks to tackle that issue.