Anybody running k3s/k8s on Hetzner using cax servers? How's that working?
We are running them at https://syself.com for six months now, after adding support for it on our platform. So far so good.
Kubernetes on Hetzner: cutting my infra bill by 75%
221–229 of 229 posts
Re: Kubernetes on Hetzner: cutting my infra bill by 75%
#222this is good well, running on bare metal would be even better
You could take a look at https://syself.com - 100% support for bare metal (I'm an employee).
Re: Kubernetes on Hetzner: cutting my infra bill by 75%
#223> While DigitalOcean, like other providers, offers a free managed control plane, there is typically a 100% markup on the nodes that belong to these managed clusters. I don't think this is true. With Digital Ocean, the worker nodes are the same cost as regular droplets, there's no additional costs involved. This makes Digital Ocean's offering very attractive - free control plane you don't have to worry about, free upg…
Besides what czhu12 mentioned, DOKS charging extra for HA control planes make me feel as if the platform is not production-grade. If you want a managed experience on Hetzner, you could take a look at https://syself.com Disclaimer: I'm an employee there
[dead]
Re: Kubernetes on Hetzner: cutting my infra bill by 75%
#224Earlier quoted context omitted.
I wholeheartedly agree, I'm trying to be generous as I know I have a bias here. I think the AWS way made clear sense in the days before the current generation of tooling existed, when we were SSH-ing into our snowflake servers (for example). But now we have tools like Kubernetes/Nomad/OpenShift/etc/etc, the logic just doesn't seem to add up any more. The main argument against it is generally of the form, "Yes, but we…
Can you recommend any resources on how to approach the topic for a startup? Most startups have very similar needs, but every single "batteries included" solution that I've encountered so far explicitly excluded infrastructure and DevOps – either because it's out of scope for the creators, or because that's what they monetize (e.g. supabase).
I don't have practical experience in that, but .NET Aspire looks like the thing you might want (and it has some support of non-.NET on both backend and frontend).
Basically the idea is that you define your infrastructure in a rather short .NET script (e.g. for example postgres + backend + frontend + auth service) and the tooling then lets you either download all the components and launch the whole thing locally, or generate a script of some kind to deploy it to an infrastructure provider (type of script depends on provider). And it provides extensive logging, monitoring, tracing etc out of the box for the majority of the included components with API endpoints and dashboards.
Re: Kubernetes on Hetzner: cutting my infra bill by 75%
#225Earlier quoted context omitted.
Honestly hetzner supoort has bren outstanding from my experience. They are always there and very responsive using email
If you prefer no bullshit communications they are great. They are to the point, terse and very German. I find this both refreshing and exactly what I want/need out of support. The few times I have needed to contact them it's been HW related. One was a SSD that was clearly having issues even though SMART reported nothing wrong, I sent them blktrace output and they said yup that checks out, scheduled disk replacement r…
I was an Internode customer for many years until TPG bought the company, fired the extremely smart and talented support team in Adelaide, and offshored "support" to a call centre in Philippines that hires people who barely know what a computer is.
I actually switched to Aussie Broadband to get an NBN fault fixed that TPG Philippines refused to acknowledge existed, or escalate to NBN.
Re: Kubernetes on Hetzner: cutting my infra bill by 75%
#226https://github.com/puppetlabs/puppetlabs-kubernetes What do the fine people of HN think about the size/scope/amount of technology of this repo? It is referenced in the article here: https://github.com/puppetlabs/puppetlabs-kubernetes/compare/...
Puppet's original design was that it was meant to be agent based on the things it was meant to configure. It was never very good at bringing up stuff before the agent could be connected. The general flow was Imager->pre-configured puppet agent->connect to controller->apply changes to make it perform as x originally it never really had the capacity to kick off the imaging/instantiation. THis meant that it scaled bette…
It's not really that much of an embuggerance.
Kickstart or cloud-init to get the OS up and Puppet agent installed, then let Puppet do the rest.
Re: Kubernetes on Hetzner: cutting my infra bill by 75%
#227https://github.com/puppetlabs/puppetlabs-kubernetes What do the fine people of HN think about the size/scope/amount of technology of this repo? It is referenced in the article here: https://github.com/puppetlabs/puppetlabs-kubernetes/compare/...
Honestly I was surprised to hear about puppet at all. Thought that was dead and buried, like chef.
Both are still extremely widely used.
Re: Kubernetes on Hetzner: cutting my infra bill by 75%
#228// Taking another slant at the discussion: Why kubernetes? Thank you for sharing your experience. I also have my 3 personal servers with Hetzner, plus a couple VM instances in Scaleways (French outfit). Disclaimer: I’m a Googler, was SRE for ~10 years for GMail, identity, social, apps (gsuites nowadays) and more, managed hundreds of jobs in Borg, one of the 3 founders of the current dev+devops internal platform (and…
> Unless you have a LOT of machines to manage, with many jobs (I’d say +250) to manage, K8s complexity, brittleness and overhead are not justifiable, IMO.
Because it looks amazing on my CV and in my promo pack.