Organizations that want to setup a K8s platform for deploying applications either need to use the managed offerings of the cloud providers or use the distributions like SUSE Rancher. The cloud provider offerings are susceptible to lock-in and there is a possibility that the costing might change. If we go in for distributions like SUSE Rancher or OpenShift, the operational cost is high since managing K8s clusters requires skilled personnel. One of the reasons for the complexity is that there are a lot of configuration knobs - various operators for different functionalities  such secrets, authentication, observability, and so on. KubeRack aims to reduce complexity by having an opinionated approach as to what to package in the distribution. For example, secrets, authentication, databases should be available by default in the distribution. Just like how a Linux distribution comes packed with lot of features, some operators need to be part of the base distribution. The cost of the having a bunch of operators available by default is possibly compute cost,  and increased attack surface. Compute costs for controllers would probably be minimal, and having security policies in place should mitigate the vulnerability due to increased attack surface. Please check here for updates.