Support Installation of Kuadrant via an Operator

[maleck13]

Use Case

As a cluster admin, I would like to install Kuadrant on to my OpenShift cluster so that I can provide my development teams with the tools needed to protect their services and APIs.

Options

Provide an Operator available via the Operator Hub that can install the Kuadrant components onto a cluster that already has Isito installed.

Questions:

• how does gateway API get installed on the cluster (cluster admin could probably do this but it needs to be a clear pre-req) another option might be to have it installed by the operator installing Istio.

Demo

• Show a cluster with Isito pre installed
• Show installing the kuadrant operator via OLM
• Show Kuadrant is configured on the cluster (Authorino is registered as an AuthProvider)
• Show the kuadrant CRDS as available

Done

• Kuadrant Operator that can install the kuadrant components (Limitador, Kuadrant Controller, Authorino)
• Add Kuadrant CRD and skeleton controller and reconcile kuadrant-controller#150
• Kuadrant Operator should create the Limitador and Authorino CR to configure Authorino and Limitador kuadrant-controller#148
• Authorino set up in Istio as a Auth GRPC service kuadrant-controller#149
• [Operator] Document how to use the operator to do installation #76
• Kuadrant Operator should inform the Kuadrant controller where limitador is deployed kuadrant-controller#157
• Kuadrant Operator is available via Operator Hub

[maleck13]

@mikenairn could you give an overview of the current state of the operator?
I believe it will setup limitador and authorino and set up their CRDS via OLM dependencies, but currently has no Kuadrant CRD for any additional setup needed

[mikenairn]

@maleck13 Yes, currently just installs the dependency operators(authorino, limitador) via OLM and deploys the controller. It currently has no reconciliation loop of it's own (kuadrant CR).