is there a selfhosted version of this ?
Show HN: Edka – Kubernetes clusters on your own Hetzner account
81–90 of 139 posts
Re: Show HN: Edka – Kubernetes clusters on your own Hetzner account
#82A bit off topic, but you might want to rethink the name. It is very close to EDEKA, the largest German supermarket chain. They have a very large IT division ( https://it.edeka ) and judging from the name of your project I was expecting it to be one of their projects.
Re: Show HN: Edka – Kubernetes clusters on your own Hetzner account
#83Re: Show HN: Edka – Kubernetes clusters on your own Hetzner account
#84Re: Show HN: Edka – Kubernetes clusters on your own Hetzner account
#85Re: Show HN: Edka – Kubernetes clusters on your own Hetzner account
#86What a great fortune to reach top of HN and get product feedback, then get rate limited by GitHub ( that was an easy fix though...) Then Hetzner gets a partial outage, failing to create new instances, causing most of the new cluster to get stuck in "creating" mode. Thanks everyone for the interest, I was not expecting this from a side project and I'll do my best to improve the platform in the future and address all f…
Re: Show HN: Edka – Kubernetes clusters on your own Hetzner account
#87https://www.reddit.com/r/hetzner/comments/18yhy89/seems_like...
Re: Show HN: Edka – Kubernetes clusters on your own Hetzner account
#88Site doesn't answer how storage is 'solved'. Is this solution uses local folder provisioning when using PostgreSQL for example.
Sorry for that, I wasn't expecting such interest. There are still undocumented parts, but happy to answer any question. It uses https://github.com/hetznercloud/csi-driver to attach persistent volumes to PostgreSQL pods.
Honestly I’m kindof surprised that something like rook it not used instead, but I guess it is easier to trust hetzner storage and hope for the best.
Re: Show HN: Edka – Kubernetes clusters on your own Hetzner account
#89Re: Show HN: Edka – Kubernetes clusters on your own Hetzner account
#90An Hetzner employee once told me that they’ve been trying for years to develop their own Kubernetes-as-a-service solution, I wonder if they’re still working on that or not.
Well, I guess from a platform that has no intrinsic IAM offering, I take that back, I guess keeping track of whose special console password is the current one is, in fact, hard work