4 ms·

Eddie from DigitalOcean here. You'll only need to pay for your worker nodes and we'll handle upgrades for you.

jacques_chester 8y ago
Could we entice someone to come do a tech-talk about it at Pivotal NYC? We're on the same avenue, after all. (And think a lot about this too)
- mejamiewilson 8y ago
  Jamie from DigitalOcean here. Yes, definitely! Most of this team is remote but myself and a couple of others are NYC based. My email is jwilson@digitalocean.com if you'd like to get in touch.
Operyl 8y ago
Then why does your marketing for early access say "get a free cluster." Is that implying that Digital Ocean will pay for the worker nodes for early adopters? EDIT: https://www.digitalocean.com/products/kubernetes/ https://www.digitalocean.com/products/kubernetes/ "Sign up for early access and receive a free Kubernetes cluster through September 2018."
- mejamiewilson 8y ago
  Jamie from DigitalOcean here. Yes users won’t pay for their workers, Block volumes or Load Balancers in early access until the end of September 2018.
  - ericpauley 8y ago
    I've found DO load balancers cannot reliably handle tls termination over 100 connections per second, and fail completely above around 300/s. Are there plans to make the load balancers more robust as part of this change? We had to switch to DNS load balancing because DO's solution simply could not scale.
    - mejamiewilson 8y ago
      Hey Eric, load balancers are getting an upgrade in the near future. Keep your eyes peeled this week!
      - ericpauley 8y ago
        That is great to hear! A few things I'd really like to see: * Ability to retrieve host health status in API * Better throughput guarantees, especially with TLS * Ability to serve from unhealthy nodes if all nodes are unhealthy * Load Balancer Health Monitoring
zegl 8y ago
I hope that there's no automatic upgrades. Kubernetes 1.10 was not fully backwards compatible with 1.9 for example.
- mejamiewilson 8y ago
  Jamie from DigitalOcean here. It will be an option as to whether you want automatic upgrades (including what times of day you’d like us to do upgrades), and we’ll go through our own internal process and testing to minimize any backwards compatibility issues.
segmondy 8y ago
Any implementation details? I would absolutely like my nodes distributed not just across different machines but also different racks. This will be key to having k8s reliability. Especially for the master nodes and wherever I've etcd running. If my k8s goes down then it needs to be because the entire datacenter is down not a machine or a rack.

Could we entice someone to come do a tech-talk about it at Pivotal NYC? We're on the same avenue, after all. (And think a lot about this too)

mejamiewilson 8y ago
Jamie from DigitalOcean here. Yes, definitely! Most of this team is remote but myself and a couple of others are NYC based. My email is jwilson@digitalocean.com if you'd like to get in touch.

Operyl 8y ago

Then why does your marketing for early access say "get a free cluster." Is that implying that Digital Ocean will pay for the worker nodes for early adopters? EDIT: https://www.digitalocean.com/products/kubernetes/ https://www.digitalocean.com/products/kubernetes/ "Sign up for early access and receive a free Kubernetes cluster through September 2018."

mejamiewilson 8y ago
Jamie from DigitalOcean here. Yes users won’t pay for their workers, Block volumes or Load Balancers in early access until the end of September 2018.
- ericpauley 8y ago
  I've found DO load balancers cannot reliably handle tls termination over 100 connections per second, and fail completely above around 300/s. Are there plans to make the load balancers more robust as part of this change? We had to switch to DNS load balancing because DO's solution simply could not scale.
  - mejamiewilson 8y ago
    Hey Eric, load balancers are getting an upgrade in the near future. Keep your eyes peeled this week!
    - ericpauley 8y ago
      That is great to hear! A few things I'd really like to see: * Ability to retrieve host health status in API * Better throughput guarantees, especially with TLS * Ability to serve from unhealthy nodes if all nodes are unhealthy * Load Balancer Health Monitoring

zegl 8y ago

I hope that there's no automatic upgrades. Kubernetes 1.10 was not fully backwards compatible with 1.9 for example.

mejamiewilson 8y ago
Jamie from DigitalOcean here. It will be an option as to whether you want automatic upgrades (including what times of day you’d like us to do upgrades), and we’ll go through our own internal process and testing to minimize any backwards compatibility issues.

segmondy 8y ago

Any implementation details? I would absolutely like my nodes distributed not just across different machines but also different racks. This will be key to having k8s reliability. Especially for the master nodes and wherever I've etcd running. If my k8s goes down then it needs to be because the entire datacenter is down not a machine or a rack.