chore: update Kubernetes section in README
Signed-off-by: m.nabokikh <maksim.nabokikh@flant.com>
This commit is contained in:
parent
a8c7ed9f67
commit
df86a1faca
@ -46,11 +46,12 @@ Because these tokens are signed by dex and [contain standard-based claims][stand
|
|||||||
|
|
||||||
For details on how to request or validate an ID Token, see [_"Writing apps that use dex"_][using-dex].
|
For details on how to request or validate an ID Token, see [_"Writing apps that use dex"_][using-dex].
|
||||||
|
|
||||||
## Kubernetes + dex
|
## Kubernetes and Dex
|
||||||
|
|
||||||
Dex's main production use is as an auth-N addon in CoreOS's enterprise Kubernetes solution, [Tectonic][tectonic]. Dex runs natively on top of any Kubernetes cluster using Third Party Resources and can drive API server authentication through the OpenID Connect plugin. Clients, such as the [Tectonic Console][tectonic-console] and `kubectl`, can act on behalf users who can login to the cluster through any identity provider dex supports.
|
Dex runs natively on top of any Kubernetes cluster using Custom Resource Definitions and can drive API server authentication through the OpenID Connect plugin. Clients, such as the [`kubernetes-dashboard`](https://github.com/kubernetes/dashboard) and `kubectl`, can act on behalf of users who can login to the cluster through any identity provider dex supports.
|
||||||
|
|
||||||
More docs for running dex as a Kubernetes authenticator can be found [here](https://dexidp.io/docs/kubernetes/).
|
* More docs for running dex as a Kubernetes authenticator can be found [here](https://dexidp.io/docs/kubernetes/).
|
||||||
|
* You can find more about companies and projects, which uses dex, [here](./ADOPTERS.md).
|
||||||
|
|
||||||
## Connectors
|
## Connectors
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user