Live data from Hacker News

DigitalOcean launches its container service

techcrunch.com

151–160 of 256 posts

Re: DigitalOcean launches its container service

#151
post #38

I'm a long time happy DO user, this is exciting. I've been managing multiple docker apps (using docker-compose) on DO for years. Is there a guide I can use to transition my apps from docker-compose to k8s? I've dabbled in k8s, but am not an expert at all. Any suggestions?

I've read the replies.

I've found that kompose does not give me the "try before you buy" experience I was hoping for.

For example, on another major cloud providers, they allow me to push up and deploy my container (stored in their registry) without even having docker installed on the client machine.

Of course, I would want to test and play with k8s before I used it in production. But, with kompose I still feel like I need to understand a lot about k8s. With docker compose I have almost forgotten everything but docker-compose build && docker-compose compose up

I think this is why Heroku was so popular. Just change git push to heroku push and try it out.

Since at least a few people align with my comment by up voting it, it seems like enough people would love an easy transition path from docker compose to k8s. This would be a killer feature for Digital Ocean: create a new cluster and then run a few well documented commands and your application is running inside DO on k8s. A guy can dream, right?

DO has always had the best documentation on just about everything technical; maybe this is just an opportunity to write up the steps? Those two documents so far, even the one from docker, still require a lot of extra reading for someone who has used docker compose for a long time.

Re: DigitalOcean launches its container service

#152
post #38

I'm a long time happy DO user, this is exciting. I've been managing multiple docker apps (using docker-compose) on DO for years. Is there a guide I can use to transition my apps from docker-compose to k8s? I've dabbled in k8s, but am not an expert at all. Any suggestions?

Kompose has been around for a little while, which essentially "compiles" your docker-compose.yml into K8S config files. However, Docker recently announced ability to deploy directly from docker-compose: https://blog.docker.com/2018/12/simplifying-kubernetes-with-... My understanding is that you'll still need to do some work, especially if you are building via compose instead of pointing to an image on a registry.

Yes, there is still a lot of work that requires a lot of knowledge about k8s. Kompose up does not just work, but it seems like DO could make that a simple set of commands with better documentation.

Re: DigitalOcean launches its container service

#153
post #118

Earlier quoted context omitted.

This is exactly what they want you to conclude. You can have a Kubernetes cluster for about $15/mo for your personal project on GKE, if you can cope with several f1-micro or a single g1-small instance hosting your workloads. That's the cost of the nodes, and that's the all-in price. Prices scale up linearly for greater capacity, just add more nodes. (Then of course I guess networking, traffic, and additional storage…

The only problem with the gke solution is loadbalancers :( It's weird that a signle LB rule costs more than the rest of the kube cluster

If you want to use your worker nodes as load balancers via Ingress, to do this on the super cheap without provisioning any Load Balancers, then you can also do that. (FWIW, DigitalOcean charges for load balancers too, and you can avoid spending on using them in the same ways. I think they are cheaper though...)

The thing to look up is nginx-ingress settings for DaemonSet and HostNetwork mode. The settings to use might be slightly different on GKE. I can give you the one-liner I use to make it work on DO/Kops, here:

helm install stable/nginx-ingress --name ingress --namespace nginx-ingress --set controller.hostNetwork=true,controller.daemonset.useHostPort=true,controller.kind=DaemonSet,controller.service.type=NodePort

That last setting about NodePort may be extraneous, I think you can skip it... actually now come to think of it, I think that is the part that prevents the ingress from provisioning a Load Balancer in front of itself.

Note of course, that there is a reason why (it is the default and) you may be inclined to purchase a load balancer, as doing it this way is fairly likely to turn out to be not only less reliable, but also super inconvenient in a lot of ways. Not "nasal demons" inconvenient, but...

Re: DigitalOcean launches its container service

#154
post #78

Hmm, now all it needs is just a comprehensive tutorial for somebody who ignored the whole container fuss so far (happy with Ansible). How to get from 0 to 100 to use Kubernetes?

It's a hard nut to crack. What I've done myself is to jump into any book published about Kubernetes and to do some online training through a couple of different MooCs. This may be a good starting point:

https://github.com/ramitsurana/awesome-kubernetes#books

https://github.com/ramitsurana/awesome-kubernetes#interactiv...

Re: DigitalOcean launches its container service

#155

Earlier quoted context omitted.

I am a mechanical engineer who dabbles in web development from time to time. I am forever indebted to DigitalOcean for creating a super easy platform for someone who has no clue about VPS starting out. I know how to operate a linux machine but not the slightest idea about how to host a website myself until I came across DigitalOcean and their LAMP/LEMP tutorials. Once I was comfortable with DigitalOcean, I tried laun…

Hi! I'm a member of the Community team at DigitalOcean. I wanted to thank you for your kind words about our tutorials. This kind of feedback means a lot to us. We're glad we could help you get your web site set up.

Thanks for the tutorials and for keeping them up to date. I’m probably not their target audience for the most part, but when I need to do something in an unfamiliar stack, [stack name] + digitalocean is usually my first search. Wish you guys had a little more of a professional oriented products (think AWS/GCP) and no ‘max 10 servers’ kind of rules so I could use it.

Re: DigitalOcean launches its container service

#157

DO'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.

As we’re layering on praise, I’d like to pile on. I’m a partner in a company in Puerto Rico. Last year immediately after Hurricane Maria hit Puerto Rico, I wrote all of our off-island service providers asking for any help they could provide. DO was one of the most generous responses. They donated 3 months of services based on our average billing. We greatly appreciated it, and the nice note they sent me showed they’r…

I believe it’s small things like this that separate the under dogs from the Giants. The giants are good if you are a huge Corp like Apple, for the little guys DO is amazing.

Re: DigitalOcean launches its container service

#158

DO'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.

I am a mechanical engineer who dabbles in web development from time to time. I am forever indebted to DigitalOcean for creating a super easy platform for someone who has no clue about VPS starting out. I know how to operate a linux machine but not the slightest idea about how to host a website myself until I came across DigitalOcean and their LAMP/LEMP tutorials. Once I was comfortable with DigitalOcean, I tried laun…

For my day job we use Azure, and it gets the job done. But all my personal projects are with Digital Ocean I love how clean and minimal everything is.

Re: DigitalOcean launches its container service

#159

Earlier quoted context omitted.

Also if your providers + OS support cloud-init, then you can express a fleet of instances which run this sort of script at boot time in something like Terraform pretty easily. Switching clouds becomes "uh... what does call their instance again?" Alternatively, pre-baking cloud images that have already run such a script and are ready to boot becomes pretty easy with a tool like Packer. Though, as the underlying OS cha…

I started using this model in '15 and it's not fragile. At all. The less I'm relying on outside frameworks, the better I sleep at night.

Certainly understandable -- I'd prefer to keep things simple and just have some kind of validation in place rather than rely on an abstraction if I can get away with it.

Having maintained various automation over the course of the past decade and a half, I can say things do change around. Over the course of only a few years though, obviously you can stick to some LTS release of whatever you're using and be pretty confident that e.g. "some-package" does not get renamed to "some-package-version" or split into "some-core" and "some-utils", or have a package get upgraded to a version with some less-than-backward-compatible configuration options, etc.

Re: DigitalOcean launches its container service

#160

DO'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.

DO's prices are why I'm a fan.
Post reply on HN