We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coming from the RFC regarding management cluster access and the plan to use azure active directory as our default identity provider
We need automation in order to scale the management of dex connectors and the required application setup as well as rotation of client secrets.
kubectl gs
The text was updated successfully, but these errors were encountered:
sketch from today
Sorry, something went wrong.
New operator lives here https://github.com/giantswarm/dex-operator still WIP
everything is in the epic already.
anvddriesch
No branches or pull requests
Coming from the RFC regarding management cluster access and the plan to use azure active directory as our default identity provider
We need automation in order to scale the management of dex connectors and the required application setup as well as rotation of client secrets.
requirements
Tasks
kubectl gs
to accept various Dex connectors on login #1592The text was updated successfully, but these errors were encountered: