4 ms·
> we needed our SaaS to also work on-prem for financial companies and government entities, and thus we could not count on kubernetes or any specific cloud vendo
by 0xbadcafebee 4y ago
> we needed our SaaS to also work on-prem for financial companies and government entities, and thus we could not count on kubernetes or any specific cloud vendor
....? kubernetes is not a cloud vendor, it runs on any Linux distribution, and it's FOSS.... ?!
- hobs 4y agoAnd that's why the sentence contains an or - because they are not a cloud provider but you cant guarantee a local corp is gonna run kube.
- tonnydourado 4y agoA previous employer had the same issue, and solved it by writing the application to kubernetes and deploying minikube to the clients that didn't have their own kubernetes cluster. To be fair, the situation ended up being: bunch of clients running minikube, 1 major client with their own kubernetes cluster, and a lot of other clients using the multi tenant, cloud hosted, offering. Made it a bit of a pain to support that one client with a cluster we could not control, but it was one of our biggest clients, so, them the breaks.
- locusofself 4y agoI mean that bringing kubernetes to an on-premises customer, just to run our software, was (probably correctly) deemed to be too much complexity. In the end it was complex enough as it was. 5 years ago kubernetes on-prem was not particularly easy, it probably still isn't, and doing it for a customer who just wants to run our software is a lot of support burden.
- ncrmro 4y agoK3os makes on prem quite nice these days