This will prevent oauth2-client removal from hydra instances removal.
At the time if you deploy an hydra in your namespace for your app and
delete it, the hydra-maester CRD will be removed, but we don't want that.
More than one project will use this CRD.
This allow to manage "Clients" with a CRD
from official doc:
The controller listens for Custom Resource which defines client registration request.
Once Custom resource is created, the controller register oauth2 client in hydra using
hydra's REST API.
Client Id, Client Secret and Identifier of the client in hydra are be stored in the
kubernetes as a secret and referenced in the applied CR. Reference is used to
identify in which kubernetes secret are stored mentioned properties.
Secret iscreated in the same namespace of applied CR. By default controller should
be deployed in the same pod as hydra. Service discovery will come in place in the future.
