oidc-gatekeeper only works with Dex as OIDC provider and Charmed Kubeflow
#159
Labels
enhancement
New feature or request
Comments
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5971.
|
DnPlas
added a commit
that referenced
this issue
Jul 25, 2024
Add a section describing how this charm can only be used as an OIDC client when Dex and Charmed Kubeflow are deployed in the model; otherwise it will fail, as there are multiple parts of this charm's code that are tightly coupled to those. Fixes #159
DnPlas
added a commit
that referenced
this issue
Jul 26, 2024
Add a section describing how this charm can only be used as an OIDC client when Dex and Charmed Kubeflow are deployed in the model; otherwise it will fail, as there are multiple parts of this charm's code that are tightly coupled to those. Fixes #159
|
Fixed by #166 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
While the OIDC Authservie is an application that can work essentially with any OIDC provider, the
oidc-gatekeepercharm 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.
The text was updated successfully, but these errors were encountered: