And with hetzner you can rent bare metal servers as well. It is somewhat equivalent to renting rack space, but they bring the servers, not you. The advantage is that if a server fails, they can provision a new one in less than 1 hour. The disadvantage is that you are probably running on somewhat refurbished hardware that has a higher prob of failing (at least these were the rumors in the past). 5-6 years ago, this was (by far) the most cost effective solution for Hadoop/HDFS deployments. IDK what the status quo is now.

As others have pointed out it is relatively easy to deploy small k3s clusters on Hetzner Cloud.

> The advantage is that if a server fails, they can provision a new one in less than 1 hour.

I can confirm that. I've been running a few servers with them and my experience is that the older ones had a failure every 2-3 years. Usually it was a disk, sometimes the power supply. Once 2 of 3 disks failed but I managed to rebuild the array (it was the HDD era so it took several hours), no data needed to be restored from backup.

But since 2018 I had no failures at all. And I'm happy to see their ecosystem grow.

> Dev teams will still operate best when they can deploy containers to Kubernetes

Jeez really? We have like, binaries deployed to machines over here.

Don’t come here speaking sense against a decade of marketing!

Realistically I wish someone would just write an orchestrator that runs Go processes and nginx and glues it all together.

> Realistically I wish someone would just write an orchestrator that runs Go processes and nginx and glues it all together.

Not quite what you're asking for but you can get close, on bare metal, with:

- ssh to set up a systemd service, scp to deploy your binary, then ssh again to restart your service

- dokku (containers are optional) with its cli

For the first option, once you've set up nginx on the server you can easily automate the addition of a new systemd service for a new app with a simple shell script. That done, it is a matter of less than a minute to add a new app and even quicker to update and restart an existing one.

For the second option, it is installed with a single bash command and supports Heroku build packs which means for many systems there's virtually (or exactly) no config needed. Just run the cli from within your app folder. If you do want containers they are automatically found and deployed too.

I've done most deployment methods from the simplest (above) through to complete Terraform builds, and once they are automated all that matters is that the method you choose supports your needs. Go for the simplest option that does that.

Can't a container mostly be a Go process?

"Marketing" as you said, made this concept of "container", but I think using the words "process" and "namespaces" is still ok.

I don't agree "container" is marketing-speak; you could say it was appropriated, but I was using linux-containers in early 2000s when it was still a kernel patch. We all knew that bare metal offers a lot and our servers are underutilized most of the time, and VMs were considered a heavier option.

I still think using "container" lose the fact that it's just a process with some tweaks :)

I'm not saying "marketing" as to say it was coined by non technical people, but rather that it's a way to "sell" the feature. Like you go see your manager and say "I'm going to containerize the application" vs saying "I'm going to add some isolation settings to the process"

Consul and nomad would like a word with you.

See my post history. No thanks :)

https://news.ycombinator.com/item?id=30020427

Binaries are so last-century, now everyone's shipping the entire OS!

Containers can contain just a single statically linked binary. Infrastructure doesn’t care.

They practically never do, nothing that you use or would read about it assumes that you do. That makes this response a little pedantic, even though it is strictly true.

It's actually quite common in the Golang world.

I still remember spending money for an FTP client that could “live edit” Perl CGI scripts on the server.

Nobody said you can't operate with old-style VMs and ansible or puppet or whatever, but tbqh yes, you're going to move slower.

It may not be fatal to your business; it's not going to be a top 3 reason you succeed or fail! But it does make a difference.

> Nobody said you can't operate with old-style VMs and ansible or puppet or whatever, but tbqh yes, you're going to move slower.

To stay in your metaphor, moving faster is not a guarantee to arrive at your target earlier. As long as everything works fine, using k8s is great. When you have to dig deep to solve a problem, a stack with less layers might be a huge advantage.

Sounds like you moved your complexity from machine virtualization to container orchestration. Doesn't sound like you won anything, least of all agility.

Is everything about to move fast? When you read a book, is it a race to get to the last page? When you sing a song, is the goal to get to the last word as soon as possible?

If you'd do it for an employer, the answer to all these questions is yes.

I deploy Kubernetes to Hetzner with https://github.com/vitobotta/hetzner-k3s