This message was deleted.

We use self hosted runners heavily, but not in a multitenant scenario. I’m not even sure you would need to separate them by namespace tbh. Assuming your users don’t have access to allow different runners in their repo, or access to modify the runners kubernetes RBAC, just setting their repo up with a preconfigured runner to use in their workflows should be sufficient

Alex Ellis from actuated has written a lot about it, you want to use microvms for isolation, if you want to run it in kubernetes, kata containers would provide isolation ( namespaces alone is not a proper way to do multi tenant isolation at least for a public product, there are too many ways to escape them, specially with runners )

@Rahul you could check out our platform for inspiration https://cloud.zeus.fyi/ai