While the OIDC Authservie is an application that can work essentially with any OIDC provider, the oidc-gatekeeper charm that tries to model it was originally designed around Dex and Kubeflow; this can be concluded by looking at the env variables in the code.
Because of that and after chatting with @kimwnasptd, it was decided that although this charm could be re-designed to work with any OIDC provider (Dex included), this team will not work on that and will keep it as it is, limiting its capabilities for Charmed Kubeflow exclusively.
What needs to get done
Update the README to specify this charm will not work outside of an environment without Dex and Charmed Kubeflow and that it cannot be used by any other application when in need of an OIDC client.
Definition of Done
The README contains clear information about what this charm can and cannot do and how it should be deployed.
Context
While the OIDC Authservie is an application that can work essentially with any OIDC provider, the
oidc-gatekeeper
charm that tries to model it was originally designed around Dex and Kubeflow; this can be concluded by looking at the env variables in the code.Because of that and after chatting with @kimwnasptd, it was decided that although this charm could be re-designed to work with any OIDC provider (Dex included), this team will not work on that and will keep it as it is, limiting its capabilities for Charmed Kubeflow exclusively.
What needs to get done
Update the README to specify this charm will not work outside of an environment without Dex and Charmed Kubeflow and that it cannot be used by any other application when in need of an OIDC client.
Definition of Done
The README contains clear information about what this charm can and cannot do and how it should be deployed.