DigitalOcean Introduces Kubernetes Product • Hacker News Board

Re: DigitalOcean Introduces Kubernetes Product

#31

Post by mejamiewilson » Wed, May 02, 2018, 3:35 PM UTC

zegl wrote: post #28

eddiezane wrote: post #24

Earlier quoted context omitted.

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

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

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.

Re: DigitalOcean Introduces Kubernetes Product

#32

Post by mejamiewilson » Wed, May 02, 2018, 3:37 PM UTC

Operyl wrote: post #27

eddiezane wrote: post #24

Earlier quoted context omitted.

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

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/ "Sign up for early access and receive a free Kubernetes cluster through September 2018."

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.

Re: DigitalOcean Introduces Kubernetes Product

#33

Post by lloeki » Wed, May 02, 2018, 3:56 PM UTC

summarity wrote: post #9

Super nice. Been running k8s on DO using Rancher, but a native solution will be really awesome. I'd like to see it as tightly integrated into e.g. GitLab like GKE is.

This will come at the right time for us, we've recently been spinning up our own k8s cluster on DO using kubeadm and flexvolume plugins, and are progressively migrating micro- and monolithic services in ascending order of criticality.

> tightly integrated into e.g. GitLab

Seconded, currently we set project integration up manually but since we're still ramping up that's not a cause of concern yet.

Re: DigitalOcean Introduces Kubernetes Product

#34

Post by ksajadi » Wed, May 02, 2018, 4:10 PM UTC

Sweet! Skycap also released the container delivery pipeline today. Can’t wait to use them together with DO Kubernetes. https://blog.cloud66.com/deploy-your-applications-to-any-kub...

Re: DigitalOcean Introduces Kubernetes Product

#35

Post by acejam » Wed, May 02, 2018, 4:23 PM UTC

manishsharan wrote: post #16

@Linode -- you guys seeing this ? Don't make me migrate away after 2 years.

I had been a Linode customer since 2008 and recently migrated to DigitalOcean about 6 months ago. So far my DO experience has been flawless. I needed basic, reliable block storage and at the time, Linode had promised "it's coming" for years. I beta-tested the Linode block storage and it was not stable for me. At the end of the day, Linode has rock solid stability, but they are unfortunately too slow to develop new features, thus I simply had to move on.

Re: DigitalOcean Introduces Kubernetes Product

#36

Post by gravyboat » Wed, May 02, 2018, 4:26 PM UTC

Operyl wrote: post #22

manishsharan wrote: post #16

@Linode -- you guys seeing this ? Don't make me migrate away after 2 years.

If you enjoy having hypervisors disappear for 12 hours without notice, go ahead. Until then, I'd say Linode is your better bet :). EDIT: A little more information, I had two VMs go offline abruptly around 1am one night. It took 3 hours for Digital Ocean to even acknowledge a problem existed (I had opened a ticket), and that was only after I started poking their twitter account. It was at least 12 hours before they br…

I'm actually looking at migrating away from Digital Ocean. I had a recent incident that took over a week to solve with 48+ hours between tickets where support wasn't even reading the previous ticket. They claimed that someone looked at the hypervisor the system was on and found nothing, but as soon as that occurred my issue was resolved. One of the worst support experiences I've ever had where I was asked for the same information multiple times after waiting days to hear back, and was even asked if my issue started during an outage that was days after my initial report. Completely unacceptable.

Re: DigitalOcean Introduces Kubernetes Product

#37

Post by gravyboat » Wed, May 02, 2018, 4:28 PM UTC

ausjke wrote: post #30

manishsharan wrote: post #16

@Linode -- you guys seeing this ? Don't make me migrate away after 2 years.

Linode user for the last 10+ years here, I'm migrating some sites to DO after checking it out recently(again), the UI is better and it seems DO innovates faster these days, and the stability might have improved too(need more time to verify this). Linode has been solid for me, only one bad hardware crash in the last 10+ years, but DO has more functions, good UI, larger disk,etc. I am trying it again.

DO support has gone majorly downhill (I have a comment about this that goes into it) in the last year or two with more issues cropping up here and there on hypervisors that go unattended for absolutely no reason. I still haven't found a good alternative but I'm looking.

Re: DigitalOcean Introduces Kubernetes Product

#38

Post by riffic » Wed, May 02, 2018, 4:36 PM UTC

Operyl wrote: post #22

manishsharan wrote: post #16

@Linode -- you guys seeing this ? Don't make me migrate away after 2 years.

If you enjoy having hypervisors disappear for 12 hours without notice, go ahead. Until then, I'd say Linode is your better bet :). EDIT: A little more information, I had two VMs go offline abruptly around 1am one night. It took 3 hours for Digital Ocean to even acknowledge a problem existed (I had opened a ticket), and that was only after I started poking their twitter account. It was at least 12 hours before they br…

architect your app around failure and loss of compute nodes - if you aren't you aren't doing cloud right.

Re: DigitalOcean Introduces Kubernetes Product

#39

Post by Operyl » Wed, May 02, 2018, 4:40 PM UTC

riffic wrote: post #38

Operyl wrote: post #22

Earlier quoted context omitted.

If you enjoy having hypervisors disappear for 12 hours without notice, go ahead. Until then, I'd say Linode is your better bet :). EDIT: A little more information, I had two VMs go offline abruptly around 1am one night. It took 3 hours for Digital Ocean to even acknowledge a problem existed (I had opened a ticket), and that was only after I started poking their twitter account. It was at least 12 hours before they br…

architect your app around failure and loss of compute nodes - if you aren't you aren't doing cloud right.

It's not that I didn't architect around the problem, that's besides the point. It's the fact they continuously have poor communication. My projects are relatively small, and were interrupted as a result of the downtime. With some effort (about 15 minutes) I brought them back up. Like I mentioned before, I use this is a testbed (the "beta" for my application) so it wasn't _terrible_. But it was still annoying.

Re: DigitalOcean Introduces Kubernetes Product

#40

Post by Operyl » Wed, May 02, 2018, 4:41 PM UTC

gravyboat wrote: post #36

Operyl wrote: post #22

Earlier quoted context omitted.

If you enjoy having hypervisors disappear for 12 hours without notice, go ahead. Until then, I'd say Linode is your better bet :). EDIT: A little more information, I had two VMs go offline abruptly around 1am one night. It took 3 hours for Digital Ocean to even acknowledge a problem existed (I had opened a ticket), and that was only after I started poking their twitter account. It was at least 12 hours before they br…

I'm actually looking at migrating away from Digital Ocean. I had a recent incident that took over a week to solve with 48+ hours between tickets where support wasn't even reading the previous ticket. They claimed that someone looked at the hypervisor the system was on and found nothing, but as soon as that occurred my issue was resolved. One of the worst support experiences I've ever had where I was asked for the sam…

And the new support system is utterly useless Javascript SPA that breaks if you refresh, or use back buttons, and is just a terrible experience to use. I get mostly NOOP responses to my tickets these days. Given how complicated Kubernetes can be, I'm terrified to see how they'll handle support for when they hit some of the more difficult problems.