-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
Add support for a backup IdP to dex-app #603
Comments
@marians will prepare a picture and explain it better :) |
Drawing is here: https://docs.google.com/drawings/d/1OnhApm0wrGKsabEwuDJrc56F-hZoJPX9JxLZSYHVWdo/edit Let't talk about it. |
Cooool proposals, I like the far right most, which is very friendly. |
That's not a spec BTW, it's there to support explanation in the team. FYI I just added these two items to the TODO list:
Currently we assume one connector for the normal user (customer) and one for Giant Swarm, the latter one being selected via the
Currently we deploy exactly two k8s-authenticator Deployments (Pod, Ingress, Service, ...). One for |
Reopened because while we do support multiple idps in dex now, we did not really document/announce how customers can set it up :) |
Checked public docs and they do mention the ability to add more than one connector |
User story
- As a customer, I want to have a way to use my backup authentication method when my Idp is down so that I can always access the management cluster.
- As a GS engineer, I want to have a backup authentication method so that I can do operations / on-call when GitHub is down.
Description
A customer asked for this option to be able to move from using
kube login
toDex
managed by us.There is also an internal use case of GitHub being a SPOF.
TODO
login
command to allow selection of the connector/IdPThe text was updated successfully, but these errors were encountered: