KEP-31: Namespace Management

[kensipe]

Signed-off-by: Ken Sipe kensipe@gmail.com

[ANeumann82]

Nice KEP! I'd really like to already see a "User Stories" section where we can describe some expectations already - and then we can decide if something is reasonable or not.

I have at least a couple in mind:

• Meta-Operator that wants to separate different parts into different namespaces. Namespaces could be prefixed with the root-operators "base" namespace.
• Meta-Operator with dependencies: Same as above, but parts of the functionality is already extracted into separate operators which are included as dependencies
• Custom Application operators in a single company: Multiple Operators that are only used in a restricted and very opinionated environment: All operators will have to install their monitoring parts into a namespace "monitoring".

[nfnt]

This is looking great, thanks for all the details of namespace management.

I added a few comments that already reflect my preference to not create namespaces in KUDO. In my opinion creating and deleting namespaces is a responsibility of the cluster admins that know best about the topology of different teams and projects in the cluster.

[zen-dog]

Nice work, however, I'd like for us to be explicit about namespace creation (see my comment about the rules)

[zmalik]

great stuff @kensipe !
LGTM as the first version of KEP and we might add more proposals later or go more in details in some alternatives

[kensipe]

Some added context for multi-namespace support:

. Istio has a component called istio-cni that has system-cluster-critical priorityclass. As of kubernetes 1.16, such deployment can only happen in kube-system namespace. Hence, we need an ability to deploy components in multiple namespaces

[ANeumann82]

Mostly nits and typos, one addition/clarification to the rules

[zen-dog]

A few grammar nits but otherwise 🚢