Partial installations and consequences for design

[thomasmaas]

One of the founding ideas of Kuadrant is that one wouldn't need to install all of it when one is looking for partial functionality . e.g. if I'm looking for operations level rate limiting and I'm not interested in auth I should be able to just install and run that part of Kuadrant; in this case: Kuadrant + Limitador.

To guarantee a good user experience, this way of thinking should probably be reflected in the way we design our CRDs: A user of a partial Kuadrant install should not be confronted with data in custom resources that has no meaning or is not accessible in their partial Kuadrant install. Or to put it in another way: a partial install of Kuadrant should give you a partial interface that exactly reflects your partial installation and nothing more.

This means we need to have a look at our CRDs: e.g. right now information related to Limitador and Authorino is stored in the same Product API CRD.

Let's discuss…

[eguzki]

As a little step forward in this direction, this PR Kuadrant/kuadrant-controller#56 makes AuthN section optional in the APIProduct. If not set, kuadrant controller will not configure the gateway and authorino in any way. Rate limit section was already optional

[eguzki]

Google doc open for discussion: https://docs.google.com/document/d/158bukTJhCEtmjx1bWoowZVFtKbaiAYeteIZj0YYCqwU

[eguzki]

@thomasmaas still think this issue is relevant and should be open?