Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DigitalOcean Introduces Kubernetes Product

digitalocean.com

Post reply on HN
Print view View original

91–100 of 100 posts

Re: DigitalOcean Introduces Kubernetes Product

#91

Post by anderiv »

tedmiston wrote: post #87
newsat13 wrote: post #75

Earlier quoted context omitted.

Yeah, DO Spaces is all around awful. Deleting is extremely slow as well. We had to write special code because DO cannot delete 1000 objects at a time (takes like 2 minutes for the api call to succeed, if it succeeds at all). To the extent that we had to just resort to delete entire buckets. The UI also keep crashing when there are many objects :(

I recently had to delete a multi-TB S3 bucket and learned that S3 isn't great at deleting tons of files either. The AWS Console just hangs forever. I let it go for hours before finding another solution.

It sounds like you’ve already resolved this, but for the benefit of any others that stumble upon this, my solution for deletion of a large bucket is to set a lifetime rule with a short TTL, after which the objects are deleted.

Set that rule, and come back to a beautifully empty bucket 24 hours later, after Amazon’s gnomes have takes care of the issue for you.

Re: DigitalOcean Introduces Kubernetes Product

#92

Post by tedmiston »

anderiv wrote: post #91
tedmiston wrote: post #87

Earlier quoted context omitted.

I recently had to delete a multi-TB S3 bucket and learned that S3 isn't great at deleting tons of files either. The AWS Console just hangs forever. I let it go for hours before finding another solution.

It sounds like you’ve already resolved this, but for the benefit of any others that stumble upon this, my solution for deletion of a large bucket is to set a lifetime rule with a short TTL, after which the objects are deleted. Set that rule, and come back to a beautifully empty bucket 24 hours later, after Amazon’s gnomes have takes care of the issue for you.

That's what I ended up with as well.

Re: DigitalOcean Introduces Kubernetes Product

#93

Post by newsat13 »

tedmiston wrote: post #87
newsat13 wrote: post #75

Earlier quoted context omitted.

Yeah, DO Spaces is all around awful. Deleting is extremely slow as well. We had to write special code because DO cannot delete 1000 objects at a time (takes like 2 minutes for the api call to succeed, if it succeeds at all). To the extent that we had to just resort to delete entire buckets. The UI also keep crashing when there are many objects :(

I recently had to delete a multi-TB S3 bucket and learned that S3 isn't great at deleting tons of files either. The AWS Console just hangs forever. I let it go for hours before finding another solution.

Yeah, S3 is not flawless but DO spaces had problems with just 5000 objects.

Re: DigitalOcean Introduces Kubernetes Product

#94

Post by mejamiewilson »

ericpauley wrote: post #77
mejamiewilson wrote: post #32

Earlier quoted context omitted.

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.

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.

Hey Eric, load balancers are getting an upgrade in the near future. Keep your eyes peeled this week!

Re: DigitalOcean Introduces Kubernetes Product

#96

Post by mejamiewilson »

timwis wrote: post #68

Does digital ocean have any equivalent of aws' RDS? Or do I have to manage my own database server?

Jamie from DigitalOcean here. A database as a service offering is on our roadmap and in discovery, and we hope to have more information about this in the near future.

Re: DigitalOcean Introduces Kubernetes Product

#97

Post by mejamiewilson »

plokiju21 wrote: post #48
mejamiewilson wrote: post #8

Earlier quoted context omitted.

Hey KenCochrane, I’m the Product Manager on this product at DigitalOcean. VonGuard is right, you only pay for the worker nodes (based on our Droplet pricing, there’s no premium) and we take care of the master. Our standard pricing lives here: https://www.digitalocean.com/pricing

Right now, GKE charges $18/month for a load balancer on top of node costs, which is costly for small scale/personal projects. Will DigitalOcean have anything similar?

Jamie from DigitalOcean here. Currently we'll deploy our DigitalOcean Load Balancer on your behalf, which is $20 a month, but we are also investigating other options. If you have any thoughts on how this should work, or what specifically you'd be looking for, I'd love to hear them.

Re: DigitalOcean Introduces Kubernetes Product

#98

Post by mejamiewilson »

Can_Not wrote: post #71
mejamiewilson wrote: post #17

Earlier quoted context omitted.

Currently it’s our $5 droplet (1GB RAM, 1 vCPU), but if you have a use case for smaller nodes I’d love to hear about it!

What about a competing product to AWS's lambda?

Jamie from DigitalOcean here. Kubernetes on DigitalOcean is the first step for us to enable more managed services like Lambda. You will be able to deploy projects like OpenFaaS or Fn very simply, but currently you would still need to determine your node pool for capacity.

Re: DigitalOcean Introduces Kubernetes Product

#99

Post by lucasyvas »

mejamiewilson wrote: post #97
plokiju21 wrote: post #48

Earlier quoted context omitted.

Right now, GKE charges $18/month for a load balancer on top of node costs, which is costly for small scale/personal projects. Will DigitalOcean have anything similar?

Jamie from DigitalOcean here. Currently we'll deploy our DigitalOcean Load Balancer on your behalf, which is $20 a month, but we are also investigating other options. If you have any thoughts on how this should work, or what specifically you'd be looking for, I'd love to hear them.

Speaking personally, I'd rather opt out of the Load Balancer altogether and instead have a floating IP automatically set up across the workers. Ingresses are easy enough to set up so that would complete the picture.

I think having the Load Balancer option is important for simplicity, but I feel a lot of DO customers (such as myself) opt to use DO for optimizing cost as well. It's a balance.

Re: DigitalOcean Introduces Kubernetes Product

#100

Post by ericpauley »

mejamiewilson wrote: post #94
ericpauley wrote: post #77

Earlier quoted context omitted.

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.

Hey Eric, load balancers are getting an upgrade in the near future. Keep your eyes peeled this week!

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

Post reply on HN