Earlier quoted context omitted.
Well, Linode fails at basic security, so...
Can I have more info on this?
Sure, pick any one of these.
https://hn.algolia.com/?query=linode%20security&sort=byPopul...
DigitalOcean launches its container service
91–100 of 256 posts
Re: DigitalOcean launches its container service
#92Earlier quoted context omitted.
Maybe you're thinking of EKS? ECS is an extremely basic scheduler that's closer to Nomad.
EKS is no more a competitor to K8S than DOK8s is a competitor to K8s. The CNCF Conformance page[1] shows a link to a spreadsheet[2] which indicates there are currently 96 products by 82 different vendors, including 34 hosted platforms like EKS, which are all Kubernetes. ECS on the other hand, is a so-called "vanilla" container service which provides its own abstractions and offers no suite for conformance, or compati…
For me, ECS having less to learn was its main appeal. You get integration with AWS load balancers giving zero down time deployment and its API to automate is very straight forward. I set it up 2 years ago and have barely touched it. I evaluated K8s at the same time and after a full day was left completely confused how to do the same thing even if I spent a full werk.
ECS has definitely got some oddities mainly in the task definition spec which is most a 1:1 with docket commands but with their own AWS stuff mixed in. Part from that the simplicity vs K8s was its biggest draw card. Lot has happened with K8s in two years I’d imagine, so same choice today might be a different story.
Re: DigitalOcean launches its container service
#93Been a user of DOs beta kubernetes service and it works well. Though I would say the title of the linked article is a bit misleading. It is a Kubernetes as a service, like EKS, GKE and AKS. But not vanilla container service a la ECS, Fargate, the former Docker Cloud, etc.
Maybe this is a dumb question, but couldn't/shouldn't a KaaS (and other orchestration systems) just be a layer on top of "vanilla" CaaS?
Don't you need to setup network paths? And connect containers to each other..
Then setup/teardown in specific order.. and if you have state, keep a subset of containers alive to avoid loosing state (even if it's replicated).
Re: DigitalOcean launches its container service
#94DO's kubernetes release is an an example of why I am a big fan. As a sole developer, I can't afford high technical debt, but DO packages tech in a way I can manage. I hope they keep on and wish other services (here's looking at you AWS) would package their services as well.
Combine it with Terraform and you're winning the Internet.
Re: DigitalOcean launches its container service
#95Earlier quoted context omitted.
https://www.terraform.io/
Is there a good way to sandbox terraform configurations? I'm not directly involved (just hear the screaming) but everything I'm hearing is that making modifications is a test of willpower. For us it's been about as transparent as a brick wall and I'm not clear if that's down to our bureaucracy or built into the design. Both are anathema to the goal of making complex deployments straightforward and self-describing (yo…
The recommended way, at least for AWS, is to have multiple accounts. One for production, and then however many more for test and development. Separate accounts let you run TF changes and know you will not impact production.
TF can be tricky to grok at first especially if you don't have everything in TF. But, I couldn't imagine managing more than a server or 2 without it or something similar at this point. Once you get into VPCs, IAMs, etc..., some type of tool is really required.
I'm also a little confused about your transparency comment. IME, tf is very clear what it is going to do in a plan. The current state files are also just json, and easy to read/search if you're not sure about something.
Re: DigitalOcean launches its container service
#96Earlier quoted context omitted.
Yes, this is the pricing model for everyone except EKS/AWS as I understand it. Manager nodes are bundled with whatever you spend on your worker nodes. Google has gone so far with GKE as to offer HA masters distributed across availability zones at no extra cost. (On the day that Amazon announced EKS general availability, if I remember correctly, which is priced at $250/mo base cost, before you even get around to spend…
Eddie from DigitalOcean here. Just want to call out that our worker node pricing is the same as our Droplets (servers). There is no price markup on using our managed service. In fact it's cheaper than deploying it yourself on DO because you don't have to pay for the master node.
Yes! Hi Eddie, I'm Kingdon we met at RailsConf :D
I've been using Kops with Digital Ocean for some time on-and-off, comparing it to the new managed offering which I've been using in limited release, and it works great (either way).
The main disadvantage of Kops being (besides that it's Alpha only, and not managed), I will pay for all of the nodes I use. It should be clear that managed k8s offers a direct cost savings pretty much everywhere it's offered.
(It would be clear, if AWS was not currently leading the broader market and offering EKS with a price model basically contradicting every other vendor's.)
Re: DigitalOcean launches its container service
#97Earlier quoted context omitted.
Yes, kubernetes
yeah, but your configs aren't fully portable between cloud providers when you look at things like LBs, storage, etc..
I thought load balancers popped out the end of Services and it was plugins that handled the specific cloud environment? I'd say that still constitutes cross platform.
Re: DigitalOcean launches its container service
#98Serious question: Is there an emerging cross platform workflow language to just write stuff to run on any cloud/container hosting setup? The idea would be to be portable, avoid vendor lock-in and take advantage price differences or quickly route around a system failure in one of the providers.
Apache libcloud works well for more basic services (e.g. storand and compute) and is extending into container management services.
Re: DigitalOcean launches its container service
#99Serious question: Is there an emerging cross platform workflow language to just write stuff to run on any cloud/container hosting setup? The idea would be to be portable, avoid vendor lock-in and take advantage price differences or quickly route around a system failure in one of the providers.
We rely on bash. Each machine that's spun up is built from scratch via one command-line call. The first half of the process interacts with each hosting API (we rely on DigitalOcean, Linode, and Vultr primarily), to build a clean slate machine with all of the packages and libraries that we expect. The second half of the process runs the actual build process, building the instance step-by-step on top of the clean slate…
Any chance you've got an open source version of this script that you could share?
Re: DigitalOcean launches its container service
#100I'm happy to see DO get some attention. I hope this means that really good hosting services like DO can still thrive in the age of AWS. DO seems to be doing well.
I agree. I've been using them for years now and their uptime and product usability has been awesome and significantly better than other hosts I've used in the past.