Korifi installation on single namespace about korifi HOT 3 OPEN

@doddisam Could you share more details on your use case?

Currently, Korifi maps orgs and spaces to kubernetes namespaces, therefore creating all resources in a single namespace is not supported. We also have the concept of a "root" namespace where some korifi metadata is stored. However, if we have a concrete scenario, we could think about how feasible it would be to support it.

cc @georgethebeatle

from korifi.

Hi George,

Thanks for the reply

We extensively run cloudfoundry on vsphere for our production grade applications. We thought of testing korifi on k8's as part of POC. we have K8's on BareMetal setup and we are only provided with the namespaces. I know korifi create separate namespaces for org/space and also we need root (cf) namespace and other namespaces for dependency install . Wanted to understand if we can setup korifi and dependencies in single namespace for POC. Can this be achieved as of today ?

from korifi.

Can this be achieved as of today

TL;DR - unfortunately not.

FWIW, I understand that a single namespace setup might have its merits. Leaving dependencies aside (as they are their own universe), a single namespace would have quite some implications:

• Korifi assumes that orgs/spaces are backed by k8s namespaces and the code assumes that an org/space guid is the underlying k8s namespace name. In a single namespace setup this assumption does not hold, one needs to think how multiple orgs and spaces can be squashed into a single namespace and adapt the code accordingly.
• User authorisation model relies on k8s RBAC and namespace-scoped roles. I am not sure how would that work out in a single namespace.
• The role bindings/secrets/service accounts propagation across org/spaces namespaces should be adjusted for a single ns scenario
• I am pretty sure there are a lot more things I cannot think off the top of my head.

If you are willing to explore this topic on your own we would be very happy to hear how it went, what challenges you faced, is such a setup feasible for a "productive" deployment, etc.

from korifi.