Edit: And if you do manged Kubernetes and managed Kafka Instances the number would go up to like 95%. Oh and those Videos with der8auer? Really awesome to see, do Linus Tech Tipps or Level1Techs next!
https://github.com/kubermatic/kubeone/tree/main/examples/ter...
Though I'm sure if you ask and they have the money for it lying around, Kubermatic will sell you an SLA.
For folks wanting to learn more, we have this nice getting started tutorial covering all the cloud providers we support including Hetzner: https://docs.kubermatic.com/kubeone/v1.5/tutorials/creating-...
And for folks asking about SLAs, support, and stuff like that, I recommend checking out our KubeOne Managed Offering: https://www.kubermatic.com/products/managed-kubermatic-kuber...
I'm also happy to answer any questions y'all might have. :)
If we're taking requests, I would love a Fargate-like service. It would be absolutely fantastic if Hetzner provided a service where users uploaded a Docker image, and Hetzner took care of handling the networking bits and running it, and gather metrics.
Upload a docker image, specify container size (1cpu 2gb)
go live
scale from 1rps to 1000 rps any time
stateless
pay per request or pay per container
AppRunner, Fargate and Cloud Run have different ergonomics and specifics but thanks for this outline. v1 is likely to be pay per container but other than that feels doable.
Superb!
> would you mind telling me a bit about the metrics and the scale you'd expect?
It will depend mostly on what the service offers.
If the service only supports running a single isolated container without any scaling whatsoever then it would be helpful if we could monitor básico stuff like CPU and memory utilization, and also network traffic, free disk space, and also disk IO. If the service supports auto-scaling then it would be helpful to track all resource utilization rates along with all alarms and events involved. Auto-scaling also implies load balancing thus if that's the case then it would also be helpful to track the basic load balancing indicators, as well as request logs.
In the end it really depends on what services you're planning on offering, and how you'll charge for it. As a user I would need to monitor any metric which is directly and indirectly involved in determining cost, and on top of that I need to monitor performance.
> Would you expect always on or more of an ephemeral container?
The most pressing need would be always on containers to be able to go the lift-and-shift onboarding route to managed services, but ephemeral containers sound like function-as-a-service and those are pretty exciting as well.
Free disk space would imply elastic block storage or something similar so I’ll need to give that a think!
V1 is very likely to be always on so great that it’s the core use case for you!
Proof: https://forum.hetzner.com/index.php?thread/21421-docker-cont...
You can find the link in my profile or here[0]
[0]: https://nimbusws.com
I have seen the "apps" in image selection in the Hetzner cloud console, so I'm convinced they're at least thinking about going up the value chain.
Would you have wanted a hypothetical discussion though (directed at grandparent), I would be up for that. Email in my profile
Disclaimer: I'm the CTO
I don't understand their price page. They claim $0 egress fees, but their free "Class A operations (mutate state)" and "Class B operations (read state)" have a mothly cap. After that you pay by the number. Isn't that an egress free?
S3 is charging $0.023 per GB, right?
IIUC - there's not a fixed cost for sending 1 GB of data. The cost differs based on where you send from and send to. So it'd be hard to have a really good estimate - but I'm wondering if anyone has a good ballpark figure.
My understanding is that transferring data on the same continent (vast majority of traffic) should be <$0.0005 - meaning the margin is really high.
I know it's more in Amazon's interest for your cloud usage to be as inefficient as possible - so they can charge you as much as possible and get as much margin as possible.
However, this product doesn't seem to make sense to me.
Why would you even pick your S3 regions? Shouldn't AWS balance your data for you across continents so that your data egress is automatically optimized?
Is that how Cloudflare works?
Bandwith cost highly depends on the scale and target network. Cloudflare has a good blogpost on relative bandwith cost: https://blog.cloudflare.com/bandwidth-costs-around-the-world...
To put numbers to the relativity, for a somewhat smaller datacenter in Central Europe with a 100Gbit/s connection, the running Cost of transit is somewhere around 0.00004€ per GB, on a theoretically fully sustained connection(not realistic, also with no redundancy or hardware). Peering is basically free(after initial buildout) with around 3k€ per 100Gbit/s (https://www.ams-ix.net/ams/pricing). This all excludes cost of investment for initial buildout and hardware. On a scale on amazons level this becomes even cheaper, since operating your own network is cheaper than buying transit.
Hetzner charges 1,19€ per TB, amazon 90$(on the first 10 TB). So amazon probably doesnt really care about the price differences per region and went with a mixed calculation, since their margins are so absurdly huge.
also, major parts of the cost are in hardware and staffing/development, of which amazon has way more, due to the demands of SDN.
One time I hosted a new movie (mkv, 23gb+), that cost like $17 to “rent” on Amazon prime… so my extended family could just take the link, download it, or just watch it in their mobile browser or laptop.
The egress of the streaming alone (not downloading), while they aircasted, definitely adds up much more than one would expect!
No thanks, I'll keep using Digital Ocean or someone who doesn't make me jump through hoops.
The only thing I imagine someone could do with the copy of my passport is pretend to be me when they sign up for a similar service.
Recently I signed up for something else from Hetzner (needed temporary storage) and they didn't request anything even though I had closed my account before so I created a new one. So perhaps they have mended their ways.
I emphasize that I personally did not run any such tests, yet. But was wondering, since this is Hetzner thread, that maybe someone can share their experience, in particular comparing AWS's gp2/gp3 based deployments vs Hetzner's volumes.
I would also add that on AWS, for example, you can nearly seamlessly expand EBS volumes in size without downtime. Last time I checked, not an option on Hetzner - you must take care of expanding the file system yourself. Which makes sense, as Hetzner is more basic service, but it's worth remembering that there are various differences like that, when comparing the day to day operations between such providers.
Network volumes always have lower iops than local disks. Thats expected, except when you pay a huge price.
> I emphasize that I personally did not run any such tests, yet. But was wondering, since this is Hetzner thread, that maybe someone can share their experience, in particular comparing AWS's gp2/gp3 based deployments vs Hetzner's volumes.
AWS GP3 has a baseline performance of 3000 iops, and from there on you have to pay for each iop/s. To reach the performance of hetzner volumes you have to add 20$/month. But with AWS you can get higher than the hetzner value. But the iops performance of the dedicated machine is not possible with gp3 (max. 16k, compared to hetzner 30-40k for local disks).
With io2 devices you can get higher than 16k iops, and higher than the hetzner local disk.
Hetzner Cloud pricing is great, but their dedicated servers are even cheaper. For example, they offer a 16-core (32-vCPU) Ryzen 9 5950X for €103 with 128GB RAM and 2 x 3.84 TB NVMe SSDs. They offer a cloud server with 32 vCPU, 128GB RAM, and 600GB of storage for €296 - nearly triple the price and those CPU cores are probably not as good since they're likely Zen2 cores rather than the Zen3 cores of the Ryzen 9 5950X.
https://www.cpubenchmark.net/cpu.php?cpu=AMD+EPYC+7502P
https://www.cpubenchmark.net/cpu.php?cpu=AMD+Ryzen+9+5950X
I know, benchmarks aren't everything, but the Ryzen is getting 1,432 per vCPU while the EPYC is getting 766.
The AX51 costs €59 for 8 Zen2 cores (16 vCPU) and 64GB RAM while the CCX41 costs €154 for 16 vCPU and 64GB RAM.
I know, the cloud servers come with flexibility, hourly billing, and no set-up fees. I also know that their cloud pricing is very good. Still, I wish I could get a few AX101s in the US. 3 AX101 servers would be €310/mo, each with 16 Zen3 cores, 128GB RAM, and 2x 3.8TB of storage.
The UX behind managing instances is delightfully pleasant where new instances are available faster than any other cloud provider we've used, within seconds of creating an instance you can immediately login with your configured SSH keys. Another nice feature is being able to "rescale" your instance to higher specs after a restart [2], so you can confidentially start with a small instance that just meets your current workload knowing that you can easily scale up your instances as your workload increases.
AWS RDS was the only critical service keeping us on AWS, a service we no longer need in our new Apps which we're building with SQLite thanks to the effortless replication in Litestream [3] that we're using to replicate to Cloudflare R2 - another great value S3 alternative with $0 egress fees [4] where you can get even greater value & performance when hosting behind their free CDN.
[1] https://servicestack.net/blog/finding-best-us-value-cloud-pr...
[2] https://bizanosa.com/how-to-upgrade-resize-hetzner-cloud-ser...
[3] https://docs.servicestack.net/ormlite/litestream
[4] https://www.cloudflare.com/products/r2/