Design decision: support multiple canvas and component namespaces on a single cluster
We saw from the start that we might need to support multiple canvas and components namespaces on a single Kubernetes cluster, but although we've tried not to prevent that happening we also haven't designed in the ability to do it, consqeuently there are a couple of things that don't work properly.
I recommend that we adopt the principle that multiple canvas and components namespaces are supported so that we can formally begin to design for it.
Design decision: support multiple canvas and component namespaces on a single cluster
We saw from the start that we might need to support multiple
canvasandcomponentsnamespaces on a single Kubernetes cluster, but although we've tried not to prevent that happening we also haven't designed in the ability to do it, consqeuently there are a couple of things that don't work properly.I recommend that we adopt the principle that multiple
canvasandcomponentsnamespaces are supported so that we can formally begin to design for it.