Key value store, allows dex to be run natively on top of a Kubernetes cluster with extremely little administrative overhead. For example, The Kubernetes API implementation, a This allows dex to meet a more diverse set of use cases instead of insisting on one particular deployment pattern. More storage backendsĭex’s internal storage interface has been improved to support multiple backing databases including Postgres, SQLite3, and the Kubernetes API through Third Party Resources. Write a config file, run the dex binary, and that’s it. There are no more special development modes instructions for running dex on a workstation translate with minimal changes to a production system.Īll of this results in a much simpler deployment story. The new architecture lacks a singleton component eliminating deployment ordering. Many components which previously had to be set through the API, such as OAuth2 clients and IDP connectors can now be specified statically. Dex is now a single, scalable binary with a sole source of configuration. Many of the changes between v1 and v2 were aimed at making dex easier to deploy and manage, perhaps the biggest pain point for dex v1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |