Ideas for a dexidp operator

[guerzon]

Hey there,

I am currently starting on a project for a dexidp k8s operator. What would you like to see in it?

Lester

[erikgb]

@guerzon Are you still working on the operator or is it done? I wondered about the same, and asked about it on the dexip Slack channel, but no responses so far.

What would you like to see in it?

For me/us an API for the management of dex clients would be most important.

[stone-z]

We (Giant Swarm) have a highly opinionated operator (dex-operator) we've built to automate the configuration of dex instances in clusters we manage. It supports mostly "dex fleet management" features like renewing app registrations and setting up default configuration. I doubt it is directly interesting for anyone else, but figured I'd mention it just in case.

[ssyno]

Hey @guerzon, @erikgb and @stone-z,

I just wanted to share a bit more about what we at Giant Swarm have built as a dex-operator for our platform needs. While ours is pretty tied to our setup reconciling our custom resources, here are some key technical challenges we tackled:

• Automated identity provider management with credential lifecycle handling by building integrations for Azure AD and GitHub with auto-cred rotation.
• Creation of an extensible architecture for supporting multiple auth providers through a common interface.
• There are some tricky bits around managing callbacks across multiple clusters.

We'd be happy to collaborate on something more general-purpose.
Could definitely share more about what worked well and what we'd do differently.