10 ms·
DigitalOcean Introduces Kubernetes Product
- mark_l_watson 8y agoI have no experience setting up Kubernetes so at the start of the year I looked at setting up a cluster on AWS. There were lots of extra expenses for a small ‘learning cluster’. I just signed up for early DO access - can’t wait!
- geku 8y agoWe launched https://www.KubeBox.com https://www.KubeBox.com beta today. You get a fully managed cluster, control plane and nodes. And you can start with a single node cluster with 8GB RAM and 2vCPU for $36/month. Additionally you can get Rancher auto-installed for managing projects, users, groups, permissions and workloads. We are in early beta but if you are interested, please sign up and we will activate your account asap. If you want to talk, we are at KubeCon Europe, contact @geku on Twitter.
- deleted 8y ago[deleted]
- flossball 8y agoPricing is key. Right now I spin up GCE based clusters as the head and version migration is free and I only pay for 2 non-preemptible adequate nodes. The rest scale and preempt somewhat cheaply as needed.
- manishsharan 8y agoCould you please share the details of your setup ? I am not familiar with Google Cloud but being able to scale up cheaply with pre-emptible instances sounds great.
- flossball 8y agoIt is just about six commands to create all the pools. gcloud container clusters create flk1 \ --cluster-version 1.XX? \ #put your version here --machine-type g1-small \ --disk-size 20 \ --preemptible \ --enable-autoupgrade \ --num-nodes 1 \ --network flk1 \ --scopes storage-rw,compute-rw,monitoring,logging-write gcloud config set container/cluster flk1 gcloud container clusters get-credentials flk1 gcloud container node-pools create small-pool-p \ --cluster=flk1 \ --machine-type n1-standard-1 \ --disk-size 20 \ --preemptible \ --enable-autoupgrade \ --num-nodes 1 gcloud container node-pools create small-pool \ --cluster=flk1 \ --machine-type n1-standard-1 \ --disk-size 20 \ --enable-autoupgrade \ --num-nodes 2 I remove the original small node once the pools are created. And then other pools for higher usage nodes.. The smallest cluster I have is about $75/month. Pre-emptible nodes seem to recover quite well and I always keep at least one container per pod/etc. on the non-pre-emptible just in case.
- minimaxir 8y agoIt works very well and has controls so you don't schedule important workloads on preemptable instances: https://medium.com/google-cloud/using-preemptible-vms-to-cut-kubernetes-engine-bills-in-half-de2481b8e814 https://medium.com/google-cloud/using-preemptible-vms-to-cut...
- eddiezane 8y agoEddie from DigitalOcean here. You'll only need to pay for your worker nodes and we'll handle upgrades for you.
- jacques_chester 8y agoCould 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 agoJamie 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 agoThen 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 agoJamie 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 agoI'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.
- jasonrhaas 8y agoGood for them! They beat AWS to it. Amazon's managed Kubernetes service is in the preview stage but should also be launched soon. How do people like Kubernetes as a production ready solution to deploy containers? I've been using Docker for a while now, just starting to mess with k8s.
- benatkin 8y ago> Amazon's managed Kubernetes service is in the preview stage but should also be launched soon. Same as DO? "DigitalOcean Kubernetes will be available through an early access program starting in June with general availability planned for later this year." I'm not sure which will be first.
- tedmiston 8y agoI had originally heard Q2 for public launch of EKS Fargate, but officially Amazon is just saying: > * AWS Fargate support for Amazon EKS will be available in 2018. https://aws.amazon.com/fargate/ https://aws.amazon.com/fargate/
- ianwalter 8y agoI resisted Kubernetes for a long time, but now that I've started using it, I think it's definitely the way to go.
- KenCochrane 8y agoToo bad they didn't list the pricing, it would be nice to know how much it will cost, once released.
- VonGuard 8y agoIt's free. Just pay for nodes.
- mejamiewilson 8y agoHey 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 https://www.digitalocean.com/pricing
- claudemiro 8y agoWill be possible to run it in a single node scenario?
- mejamiewilson 8y agoYes, you’ll be able to spin up a single node cluster.
- misframer 8y agoWill there be a minimum size for a worker node?
- mejamiewilson 8y agoCurrently 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!
- Can_Not 8y agoWhat about a competing product to AWS's lambda?
- minxomat 8y agoSuper 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.
- thepumpkin1979 8y agoRancher 2.0 was just announced today, 100% Kubernetes-based https://news.ycombinator.com/item?id=16976934 https://news.ycombinator.com/item?id=16976934
- eganist 8y agoFor the curious: k8s is a specific kind of contraction -- a https://en.wikipedia.org/wiki/Numeronym https://en.wikipedia.org/wiki/Numeronym. Other examples include i18n = internationalization.
- lloeki 8y agoThis 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.
- eulid55 8y agoSounds like DO is going to have the cheapest k8s service out there!
- deleted 8y ago[deleted]
- technofiend 8y agoFor some free lab time until the new commercial offerings arrive, try play with k8s: https://labs.play-with-k8s.com/ https://labs.play-with-k8s.com/
- manishsharan 8y ago@Linode -- you guys seeing this ? Don't make me migrate away after 2 years.
- Operyl 8y agoIf 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 brought it back online, it was never acknowledged in any mass ticket. If you are unlucky enough, you can have the same thing unfortunately happen to you. This is my second experience of having such an outage at Digital Ocean and is, as a result, the reason I still only use DO as a testbed and nothing more. EDIT2: Another pretty bad example of Digital Ocean: https://status.digitalocean.com/incidents/8sk3mbgp6jgl https://status.digitalocean.com/incidents/8sk3mbgp6jgl.
- gravyboat 8y agoI'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.
- Operyl 8y agoAnd 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.
- vegardx 8y agoHow are you guys sorting out networking?
- mejamiewilson 8y agoJamie from DigitalOcean here. VPC is coming to DigitalOcean and the cluster will live within a VPC. Past that there are a lot of details! Is there something specific you're interested in?
- deleted 8y ago[deleted]
- segmondy 8y agoGood, I have been debating between running my own k8s on DO vs GKE. I'm glad I don't have to build my own cluster. I think I'm going to do both for now tho. If DO is mature and stable I'll kill the GKE cluster.
- ksajadi 8y agoSweet! 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-kubernetes-cluster/ https://blog.cloud66.com/deploy-your-applications-to-any-kub...
- joshuatalb 8y agoI have some questions, mainly around networking and the like. Is there somebody from DO that I can get in touch with directly? Thanks.
- al3xnull 8y agoSecond on the network. My concern is around inter-node traffic and if it's segmented or like their current private networking.
- mejamiewilson 8y agoHi, Jamie from DigitalOcean here. We will have VPC support on DigitalOcean by the time we go live. But if you want to talk in more detail, my email is jwilson@digitalocean.com
- whitepoplar 8y agoMy only wish is for DO to allow customers to bring-your-own IP blocks. Vultr has this, but seems less robust to run a business on.
- ryanworl 8y agoCheck out packet.net if you haven’t already, they offer that and some other networking features you don’t see typically from VPS providers.
- whitepoplar 8y agoPacket is nice, but way more expensive than DO.
- ra1n85 8y agoWhy?
- jorams 8y agoThis is a great development, but I'll have to wait and see how reliable it actually is. I've had a few droplets running with them over the years, and that has been rock solid (years of uptime on one droplet, no problems whatsoever), but we recently started using Spaces for a commercial product and it has been a catastrophe. There are connectivity issues leaving the service mostly unavailable on a regular basis, and the status updates about it aren't particularly timely. While trying to migrate away to GCS, synchronizing data (using gsutil) has proven practically impossible. The API is incredibly slow to list objects and occassionally responds with nonsensical errors. (Every once in a while a random "403 None" appears, causing gsutil to abort. We could probably work around that by modifying gsutil to treat 403 as retry-able, but since overall performance is so awful and we can regenerate most data, we decided to give up.)
- newsat13 8y agoYeah, 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 :(
- riffic 8y agoI’ll assume Spaces works like S3 in where updates and deletes are eventually consistent, not immediately consistent: https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html#ConsistencyModel https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction...
- tedmiston 8y agoI 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.
- anderiv 8y ago
- Rotareti 8y agoI'm currently running multiple Kubernetes clusters using StackPoint in combination with DigitalOcean. This has been working very well. Could someone tell me how the new DO Kubernetes service compares to StackPoint?
- yebyen 8y agoYou're paying for master nodes with StackPoint, right? Each droplet you start has the same cost structure whether it's running your "user-land" slave workloads or if it's there just for running your cluster. The big payoff (for small clusters like mine anyway) is that masters won't be charged, like other managed Kubernetes offerings from Azure and Google. I don't know enough about StackPoint to compare it to a service I haven't even seen in beta yet, but I can tell you that much. I know that StackPoint is supposed to be "like a managed" experience. Maybe one of the DigitalOcean guys who has been responding in this thread can speak to the technical details of the new offering.
- Rotareti 8y ago> You're paying for master nodes with StackPoint, right? No, you pay a monthly subscription (starting at 50$/month). The service allows you to create/update clusters easily. I'm not sure, but I think you can create as many clusters as you want with a 50$ subscription (at least I never hit a limit). The procedure to create a new cluster looks something like this, if you use the web interface: * click "add cluster" * select cloud provider (DO, AWS, GKE, etc.) * configure master nodes. E.g.: 2 master nodes @ 2G Ram, running in region NYC1. * configure worker nodes. (same procedure as with master nodes) * submit If you choose DO, you get a cluster that works with DO load-balancers, DO block-storage, etc out of the box. If a new version of Kubernetes is released, you can hit the "update cluster" button. They have an API for all the stuff too. I chose StackPoint in combination with DO, because it felt least bloated and least locking-in. Now that DO introduces the Kubernetes service, I can imagine that I won't need the StackPoint subscription any more.
- yebyen 8y agoThat's very interesting, thanks for sharing. $50/mo is a bit for a hobbyist, but not much if you're operating at any serious kind of scale! But I mean, in addition to the StackPoint subscription, you do also pay for the master node droplets when you use it, as well as paying for the worker droplets, right? You won't be paying for those masters anymore with the managed offering, from any of the cloud vendors I've heard of announcing a managed offering. I have to imagine this is because they can do (or plan to do) multi-tenant APIs under the hood. (Even if you get a pool of worker nodes and the pool is on machines that are exclusively yours, it seems unlikely that your constellation of masters is ever going to be exclusively yours unless your bill says "dedicated masters" and you've paid something for it... and that's fine, as long as it's done right! I obviously can't afford to give myself as many masters as a multi-tenant system can allocate a share on for me. We will all wind up getting more resilient systems out of the deal, and for much cheaper, in this arrangement I think.) I'm definitely signing up for this preview, I hope it will include an API for creating/upgrading/tearing down clusters! I can't imagine it will do anything but obsolete StackPoint for DigitalOcean customers. Then again, maybe the bigger value provided by StackPoint is actually that you can take this K8S cluster orchestrator with you to a different cloud if you need to move. It is obviously going to be a harder sell though, when all of the major vendors are coming out with their own managed k8s offerings that enable cost savings. Next to $50/mo, enough masters to make your cluster resilient against localized failures on a 24/7 basis are... pretty costly, right? It's really going to come down to, are the managed offerings as good, better, etc than the ones you can install yourself with a tool like kops (or are they as good as the ones that a service such as StackPoint can help you install for yourself?) I wonder, did you try installing Kubernetes for yourself before you tried StackPoint? If so, what distro(s) did you try and which ones did or didn't make the cut?
- ksec 8y agoSo, Kubernetes basically won? Nomad and Swarm don't stand a chance, but what about Mesos or DC/OS?
- Already__Taken 8y agoI don't know if nomad is going for the same problem is it? It seems a great deal simpler to use
- cytzol 8y agoKubernetes is the Git of container orchestration. It doesn't matter if any other products are better when k8s has, like, 99% of the mindshare!
- ksec 8y agoSigh. You like BSD? Let the world have Linux. You like Hg? Let the world have Git. You like DC/OS? Let the world have Kubernetes. But they all lost.
- tedmiston 8y agoMesosphere is still a player, but they have also recently added Kubernetes support in DC/OS. https://kubernetes.io/docs/getting-started-guides/dcos/ https://kubernetes.io/docs/getting-started-guides/dcos/
- jasonrhaas 8y agoEverything I'm seeing right now in the market is saying that.. yes Kubernetes has won, or IS winning.
- devmunchies 8y agoFantastic. Any plans for a managed DB offering (Postgres) so the whole stack can be managed?
- timwis 8y agoDoes digital ocean have any equivalent of aws' RDS? Or do I have to manage my own database server?
- mejamiewilson 8y agoJamie 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.