Skip to content
This repository was archived by the owner on May 17, 2024. It is now read-only.

Commit d997b73

Browse files
committed
Rephrase both -> all
Signed-off-by: Christian Simon <[email protected]>
1 parent c33b54e commit d997b73

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

demo/README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,13 @@
33
This document will walk-through how to create three managed Kubernetes clusters on
44
separate providers (Google, Amazon and Digitalocean), deploying:
55

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.
78

89
- [Gangway](https://github.com/heptiolabs/gangway) web server to authenticate
910
users to Dex and help generate Kubeconfig files.
1011

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
1213
clusters to OIDC authentication.
1314

1415
- [Contour](https://github.com/heptio/contour) as the ingress controller with
@@ -78,9 +79,8 @@ CLOUD=digitalocean make terraform_apply
7879

7980
This will create a Kubernetes cluster in EKS and GKE, a Service
8081
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.
8484

8585
## Configuration
8686

0 commit comments

Comments
 (0)