We have reenabled the creation of new resources in SFO2 for all customers.
We have deprecated our legacy load balancer scaling system in all datacenter regions. This includes the deprecation of the do-loadbalancer-size-slug annotation for DigitalOcean Kubernetes load balancers.
Horizontal scaling is now available in all regions.
You can now customize the amount of time a load balancer allows HTTP connections to remain idle before closing it. The maximum amount time you can set is 600 seconds (10 minutes).
Setting a custom time out length has no effect on HTTPS and HTTP/2 forwarding rules using TLS passthrough.
DigitalOcean Load Balancers and DOKS load balancers now support the HTTP/3 protocol.
The following pricing changes are now in effect:
A new $4 Droplet with 512MB of memory, 10GB of storage, 1 vCPU, and 500GB of outbound data transfer is now available in NYC1, FRA1, SFO3, SGP1, and AMS3. The slug is s-1vcpu-512mb-10gb.
We have simplified pricing for DigitalOcean Kubernetes and some Managed Databases for better accuracy and predictibility.
The prices of Droplets, Snapshots, Load Balancers, Reserved IPs, and Custom Images have increased.
There is no change to pricing for Spaces, backups, volumes, DigitalOcean Container Registry, or App Platform. There are also no changes to inbound data transfer or bandwidth pricing.
This is our first major price change in 10 years, and we believe the new model better fits our understanding of our customers and the expanded breadth of our offerings. For a more detailed breakdown of the changes, see our blog post on our new pricing.
In order to improve security, DigitalOcean no longer accepts TLS 1.0 and TLS 1.1 connections. This includes connections to www.digitalocean.com, cloud.digitalocean.com, and api.digitalocean.com.
UDP support is now available for all DigitalOcean Load Balancers. This includes UDP support for DOKS load balancers.
To use UDP for DOKS load balancers, clusters must use Kubernetes version 1.21.11-do.1, 1.22.8-do.1, or higher.
We have started rolling out UDP support for DigitalOcean Load Balancers. This includes UDP support for DOKS load balancers.
Managed Let’s Encrypt certificates will begin using Elliptic Curve Digital Signature Algorithm (ECDSA) instead of RSA. ECDSA is equally secure and more computationally efficient than RSA. ECDSA certificates follow the shorter root chain and aren’t rooted using the DST Root CA X3 cross-sign which expired on 30 September 2021.
As we roll out this change, new Let’s Encrypt certificates provisioned for DigitalOcean Load Balancers and Spaces will increasingly use ECDSA and existing certificiates secured with RSA will be secured with ECDSA upon auto-renewal. This change doesn’t require any action from DigitalOcean customers.
You can now resize load balancers once per minute, instead of once per hour. The cost is prorated based on how long the load balancer operates at each size, with a minimum charge of $0.01.
You can now scale load balancers with more granularity by adding or removing nodes. The number of nodes a load balancer contains determines how many simultaneous connections and requests per second it can manage.
Each additional node increases the load balancer’s maximum:
You can add up to 100 nodes to a load balancer.
We have deprecated TLS DHE ciphers for all load balancers.
Released v1.65.0 of doctl, the official DigitalOcean CLI. This release includes a number of new features:
--ha flag was added to the kubernetes cluster create sub-command to optionally create a cluster configured with a highly-available control plane. This feature is in early availabilitykubernetes cluster sub-commands now include a “Support Features” field when displaying version options--disable-lets-encrypt-dns-records flag was added to the compute load-balancer create sub-command to optionally disable automatic DNS record creation for Let’s Encrypt certificates that are added to the load balancerYou can now opt out of DigitalOcean automatically creating DNS records for Let’s Encrypt certificates during SSL certificate creation, load balancer creation, and SSL forwarding rule management.
The load balancer and Spaces services now support wildcard Let’s Encrypt certificates.
You can now resize load balancers to better match their performance to their workload.
Fixed a bug with DigitalOcean Load Balancers that prevented outbound data transfer from Droplets from being added to bandwidth usage totals. Any inconsistencies will be updated on the April invoice.
Load balancers now come in small, medium, and large sizes. The larger the load balancer, the more simultaneous connections and requests per second it can manage. Existing load balancers are now considered “small” load balancers and are unaffected by this change.
Load balancer health checks now support the HTTPS protocol. You can now configure load balancers to verify the health of your Droplets’ HTTPS endpoints.
The SFO3 datacenter region is now available.
v1.18.0 of the DigitalOcean Terraform Provider is now available. This release includes support for the backend keepalive option for the load balancer resource and data source.
Load balancers now allow you to set a keepalive option for target Droplets.
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.
DigitalOcean Load Balancers no longer support downgrading TLS connections to TLS 1.1.
DigitalOcean Load Balancers no longer support downgrading TLS connections to TLS 1.0. We will stop supporting TLS 1.1 later this year.
DigitalOcean Load Balancers now support PROXY protocol version 1.
Pricing for load balancers has decreased from $20/month to $10/month.
Load Balancers v1.5 is released to general availability in all regions, including backend upgrades, Let’s Encrypt Integration, and HTTP/2 Support.