Kubernetes API Now In General Availability
Today, we are promoting the Kubernetes API to General Availability. As part of this release, we have also extended the API with additional functionality:
When creating or updating a cluster, you may now configure a maintenance window policy specifying the day of the week and time of day that updates should take place for the cluster. Additionally, setting a cluster’s
truewill specify that the cluster can be automatically upgraded to new Kubernetes patch releases (e.g. 1.13.1 to 1.13.2) during its maintenance window.
upgradeendpoint is now available to imminently trigger an upgrade to a newer patch release of Kubernetes at your own convienience. You may list available upgrades for your cluster using the
In order to give users finer control over individual nodes, the
recycleendpoint has been deprecated. Instead, we now offer the ability to delete or replace specific nodes in a node pool. By default, workloads will be drained from the node before deletion. Appending the
skip_drain=1query parameter to the request will cause the node to be imminently deleted. Appending the
replace=1query parameter to the request will cause the node to be replaced by a new one after it has been deleted.
For the full details, see the API reference documentation for Kubernetes.
Thank you to everyone who took the time to provide us with feedback.