This repository was archived by the owner on May 17, 2024. It is now read-only.
File tree Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Original file line number Diff line number Diff line change 3
3
This document will walk-through how to create three managed Kubernetes clusters on
4
4
separate providers (Google, Amazon and Digitalocean), deploying:
5
5
6
- - [ Dex] ( https://github.com/dexidp/dex ) as the OIDC issuer for both clusters.
6
+ - [ Dex] ( https://github.com/dexidp/dex ) as the OIDC issuer for all clusters
7
+ running only in the master cluster.
7
8
8
9
- [ Gangway] ( https://github.com/heptiolabs/gangway ) web server to authenticate
9
10
users to Dex and help generate Kubeconfig files.
10
11
11
- - [ kube-oidc-proxy] ( https://github.com/jetstack/kube-oidc-proxy ) to expose both
12
+ - [ kube-oidc-proxy] ( https://github.com/jetstack/kube-oidc-proxy ) to expose all
12
13
clusters to OIDC authentication.
13
14
14
15
- [ Contour] ( https://github.com/heptio/contour ) as the ingress controller with
@@ -78,9 +79,8 @@ CLOUD=digitalocean make terraform_apply
78
79
79
80
This will create a Kubernetes cluster in EKS and GKE, a Service
80
81
Account to manage Google Cloud DNS records for DNS challenges and OIDC secrets
81
- for both clusters. It should generate a JSON configuration file for both
82
- clusters in ` ./manifests/google-config.json ` and ` ./manifests/amazon.json `
83
- respectively.
82
+ for all clusters. It should generate a JSON configuration file for all clusters
83
+ in ` ./manifests/[google|amazon|digitalocean]-config.json ` respectively.
84
84
85
85
## Configuration
86
86
You can’t perform that action at this time.
0 commit comments