N/A

this would be better received in <#1157406325593096264>, the team can kick off a discussion with you there

Sure thing!

What would be the reason to run k8s on Railway?

(Just curious because like, our goal is to like…replace it lol)

tbh im fine with no kubernetes support, i dont care that much, but one of my use cases would be to learn and mess around with kubernetes. Doing that in Railway would be pretty nice but whatever

poke

Yea fair nuff. I think at best we'd support importing stuff from like, Helm (in the same way we support docker-compose)

Kubernetes is a really, really inefficient system

i mean, if VMs are really coming and they can host a kubernetes cluster would be pretty nice

i understand that Railway supporting Kubernetes makes no sense

Beautiful thing about opensource and leaning into opensource; you can just do things

even tho I would like a guide on how to set it up, even if its a simple control and worker node

even if railway doesn’t “natively” support kubernetes, I’m sure people will make templates for it after v3 is out

i’d call that near enough to railway supporting it natively

Just freedom of using a FOSS platform (K8s) I like on a hosted platform (Railway) I like. Easy enough to run it outside of Railway, no stress, just figured I'd ask. Good to have an extra competitor for pricing, uptime, community and such

Excellent point my man!

This is dope, pretty much what I was thinking (hence why I said "or Kubernetes resources")

Would love expansion on this

Oh just from a platform perspective. We don't use it internally because it's orders of magnitude less efficient

The reconcilation loop, CRDs, etc are consistently tracking and reconcilling objects with no deltas. And when there IS a delta, there's locks everywhere so things end up being really slow

So, once it left Google, with great intentions, to become "A general purpose container orchestrator that runs anywhere", it got coopted by the community, and then everyone wanted something different from it

So they implemented all of that, on top of a design that ends up bottlenecking under that complexity

And so like, we would never implement the CRDs, and thus it wouldn't be kube compatible (100%)

Lol, that is such a good writeup, i feel you man. Dont disagree

Classic case of complexity evolution…its really interesting that it became a colloquial standard. It makes sense in theory but i do hear what you are saying. Overall we are cycling (perpetual?)

Overall i am a sucker for Kube API but i do agree about its flaws and you have good points. Not married to it long-term, just enjoy it rn

esp the eco around it.

So does railway support compose or not

Damn it I got lost

supported as an import method for creating a template

alr but is the template part necessary? I don't expect railway to create a docker swarm for me or something, but creating a project from compose would be noice