undefined | Better HN

0 pointsstevefan19994mo ago0 comments

I'm working on a K8S hosting solution that just gives the user a simple Kubernetes cluster. I (or we) handle the compute, (networked) storage and ingress hosting for you, and the cluster provision time should be within minutes.

You just need to pay for a fixed monthly upfront cost rather than PAYG, giving small developers a good save of their money.

In other words, this is similar to self hosting with K0S/K3S/OpenShift, except you don't have to own servers to begin with, in other words, it is a little similar to serverless K8S.

Well, all you those you can actually do with a VPS today, heck why do I have to do it if EKS/GKE/LKE/OKE/DOKS exists? That's because it takes a lot of time to properly setup VPC/EBS/S3/EC2, you need to pay an insane amount of premium and overheads to those while an ordinary user just don't want to hassle too much.

I want to undercut the big clouds by saving people's money and time. I have had enough of seeing a ludicrous EKS billing. I just want K8S to be the control panel of everything.

Deploy, run and scale later, simple as that

0 comments

myguestacc4mo ago

This resonates with my experience as a small startup dev. I wouldn't mind bringing my own servers for running my apps but for k8s I need at least 3 control nodes in each cluster and I need multiple clusters to cover different parts of the world. All those control planes are idling most of the time but cost money and effort to keep them alive. I'm sure those could be shared among dozens of users. Is this something you are going to support? Or I'll also have to rent the worker nodes from you?

stevefan1999OP4mo ago

You rent the compute, storage and network from the worker clusters at a fixed monthly price as one budget package, just like how you buy VPSes back in the days (think EC2 Lightsail or Linode, except now you just have a K8S context). You can choose multiple geolocations, but I'm still looking for a successful lab simulation first.

Right now I'm hosting my own test cluster under my bed so I can't show it.

You don't have to manage CNI, CSI, Linux kernel, etcd. You just need Kubernetes app development knowledge and that's basically it.

Now I'm still thinking about how to get live migration and failover working, so it is going to take a painful while...Kata Container doesn't support it out of the box but Cloud Hypervisor does

calind4mo ago

Link? :)

stevefan1999OP4mo ago

No link yet as I'm still just a solo dev, the (hobbish?) project is crawling very slowly, but I have the general architecture in mind. I need to get the frontend first.

I tried to submit it as a startup project last year but the feedback isn't great, I want to have something polished first before making it public

j / k navigate · click thread line to collapse

0 pointsstevefan19994mo ago0 comments

You just need to pay for a fixed monthly upfront cost rather than PAYG, giving small developers a good save of their money.

In other words, this is similar to self hosting with K0S/K3S/OpenShift, except you don't have to own servers to begin with, in other words, it is a little similar to serverless K8S.

I want to undercut the big clouds by saving people's money and time. I have had enough of seeing a ludicrous EKS billing. I just want K8S to be the control panel of everything.

Deploy, run and scale later, simple as that

0 comments

myguestacc4mo ago

stevefan1999OP4mo ago

Right now I'm hosting my own test cluster under my bed so I can't show it.

You don't have to manage CNI, CSI, Linux kernel, etcd. You just need Kubernetes app development knowledge and that's basically it.

Now I'm still thinking about how to get live migration and failover working, so it is going to take a painful while...Kata Container doesn't support it out of the box but Cloud Hypervisor does

calind4mo ago

Link? :)

stevefan1999OP4mo ago

No link yet as I'm still just a solo dev, the (hobbish?) project is crawling very slowly, but I have the general architecture in mind. I need to get the frontend first.

I tried to submit it as a startup project last year but the feedback isn't great, I want to have something polished first before making it public

j / k navigate · click thread line to collapse