Kubernetes v1.7.0 This version will be available for new clusters and opt-in master upgrades according to the following planned schedule:
Kubernetes 1.7 is being made available as an optional version for clusters. Please see the release announcementfor more details on new features.
You may now expose Kubernetes services by internal load balancing. This is a Beta feature that lets your Kubernetes and non-Kubernetes services access one another on a private network.
You can now use HTTP re-encryption through Google Cloud Load Balancing to allow HTTPS access from the GCP Load Balancer to your service backend. This feature ensures that your data is fully encrypted in all phases of transit, even after it enters Google's global network.
Support for all-private IP (RFC-1918) addresses is generally available. These addresses allow you create clusters and access resources in all-private IP ranges, and extends your ability to use Container Engine clusters with existing networks.
Support for external source IP preservation is now generally available. This feature allows applications to be fully aware of client IP addresses for Kubernetes services you expose.
Cluster autoscaler now supports for scaling node pools to 0 or 1, for when you don’t need capacity.
Cluster autoscaler can now use a pricing-based expander, which applies additional cost-based constraints to let you use auto-scaling in the most cost-effective manner.
Cluster autoscaler now supports balanced scale-outs of similar node groups. This is useful for clusters that span multiple zones.
You can now use API Aggregation to extend the Kubernetes API with custom APIs. For example, you can now add existing API solutions such as service catalog, or build your own.
The following new features are available on Alpha clusters running Kubernetes version 1.7:
Known Issues with v1.7.0 Kubelet certificate rotation is not enabled for Alpha clusters. This issue will be fixed in a future release.
Known Issues with v1.7.0: