search

kudobuilder / kudo

Kubernetes Universal Declarative Operator (KUDO)
https://kudo.dev
Apache License 2.0
1.18k stars 101 forks source link

KUDO CRDs are all Namespace scoped #275

Open jbarrick-mesosphere opened 5 years ago

jbarrick-mesosphere commented 5 years ago

What would you like to be added:

The Framework and FrameworkVersions CRDs are namespace scoped, which doesn't make a ton of sense as most likely FrameworkVersions should be provided to the entire cluster (whereas, Instances should be namespace scoped).

https://github.com/kudobuilder/kudo/blob/master/config/crds/kudo_v1alpha1_framework.yaml#L13

I'm not sure if there's a reason for this or if this should be a KEP, but I'll start with a ticket.

gerred commented 5 years ago

@runyontr and I talked about this in the past and namespacing at the time made sense for a multi-tenant cluster where you may only want certain Frameworks and FrameworkVersions available to certain namespaces. Beyond that, there hasn't been a compelling reason to go either way. Would love more thoughts on that.

Probably no need for a KEP, could extend the language in KEP-9, or bolt this on to a future security/RBAC KEP and keep it as an issue for now.

jbarrick-mesosphere commented 5 years ago

I've also written controllers before that support either namespace or cluster scoping - we could make it configurable.

kensipe commented 4 years ago

@jbarrick-mesosphere @gerred are we still looking for this?

kensipe commented 4 years ago

we could use reasons / justifications and prioritization