You can now do the following on Kubernetes clusters:
Use surge upgrade when upgrading an existing cluster. Surge upgrade is enabled by default when you create a new cluster.
Move a Kubernetes cluster and its associated resources, such as Droplets, load balancers and block storage volumes, to a project using the DigitalOcean control panel or
doctl command-line tool. You can also assign a project when you create a new cluster. If you do not specify a project, it gets assigned to the default project.
Due to capacity limits in the region, we have disabled the creation of new resources in SFO2 for new customers. Existing customers with resources in SFO2 are unaffected and can still create and destroy resources in SFO2.
On Kubernetes 1.19 and later we now provision two fully-managed firewalls for each new Kubernetes cluster. One firewall manages the connection between worker nodes and control plane, and the other manages connections between worker nodes and the public internet.
You can now apply taints to Kubernetes node pools using the DigitalOcean API. When you configure taints for a node pool, the taint automatically applies to all current nodes and any subsequently created nodes in the pool. For more information, see Kubernetes' documentation on taints and tolerations.
The SFO3 datacenter region is now available.
The DigitalOcean Virtual Private Cloud (VPC) service is now available for all customers. VPC replaces the private networking service. Existing private networks will continue to function as normal but with the enhanced security and features of the VPC service. See the description of VPC features for more information.
We began the incremental release of the DigitalOcean Virtual Private Cloud (VPC) service. It will be available for all customers soon. VPC replaces the private networking service.
v1.14.0 of the DigitalOcean Terraform Provider is now available. This release includes a bug fix for projects containing many resources and exposes the Droplet IDs for individual nodes in Kubernetes clusters.
Released v1.38.0 of doctl, the official DigitalOcean CLI. This release adds the ability to set Kubernetes node pool labels as well as support for deleting multiple Kubernetes clusters with a single command.
DigitalOcean Container Registry has been released in Beta. To request early access, visit the homepage for Container Registry.
DigitalOcean Kubernetes has added native support for the Kubernetes Dashboard for all DOKS clusters.
The DigitalOcean Kubernetes (DOKS) October release is now available, and contains the following new features:
6-hour and 1-day alert policies for Droplets and Kubernetes worker nodes have been deprecated. No new alert policies with these intervals can be created. Existing alert policies using these intervals will remain in place until 1 August 2019, at which point they will be modified to reflect a 1-hour interval.
DOKS node pools can now be named at creation time.
DOKS master nodes now automatically rotate logs to avoid disk space issues.
DOKS customers will now be able to see the cost of their Kubernetes nodes and load balancers aggregated by cluster name within a Kubernetes clusters group on their invoice. Block storage volumes or block storage volume snapshots used in a DOKS cluster are not yet included in the cluster aggregation.
API support for Kubernetes Limited Availability was made publically available to all users who opt-in. This included API documentation and support in official clients (godo, doctl, droplet_kit).
The following updates were released for DigitalOcean Kubernetes:
The minimum size for a Kubernetes node was changed to the 2 GB Memory / 1 vCPU plan.