4 ms·
No documentation of how to self host yet. It's not hard, it requires K8S and S3 compatible object store. We want to harden Neon operationally before documenting
by nikita 4y ago
No documentation of how to self host yet. It's not hard, it requires K8S and S3 compatible object store. We want to harden Neon operationally before documenting and supporting on prem production installs.
- ccakes 4y agoRequires k8s as in - uses k8s APIs? Or is supported on k8s? Apologies haven’t read the docs but wanted to highlight this. A hard requirement on k8s to the exclusion of other schedulers would be a shame and an odd choice
- mattashii 4y agoWe've built our current cloud offering on k8s, and that is our only scale-to-0 implementation. That does not mean that you cannot run Neon outside k8s, but we are not actively maintaining nor supporting other hosting options.
- rubenfiszel 4y agoGot it, makes sense. I think we are pursuing similar strategies with OSS/self-hostable products. I would love to get in touch with you about it. Could you drop me an email at ruben@windmill.dev ?
- nikita 4y agoReplied