@@ -40,7 +40,7 @@ Directions on how to deploy OIDC authentication with multi-cluster can be found
4040
4141### Quickstart
4242
43- Deployment yamls can be found in ` ./demo /yaml ` and will require configuration to
43+ Deployment yamls can be found in ` ./deploy /yaml ` and will require configuration to
4444an exiting OIDC issuer.
4545
4646This quickstart demo will assume you have a Kubernetes cluster without OIDC
@@ -54,7 +54,7 @@ This will create it's Deployment, Service Account and required permissions into
5454the newly created ` kube-oidc-proxy ` Namespace.
5555
5656```
57- $ kubectl apply -f ./demo /yaml/kube-oidc-proxy.yaml
57+ $ kubectl apply -f ./deploy /yaml/kube-oidc-proxy.yaml
5858$ kubectl get all --namespace kube-oidc-proxy
5959```
6060
@@ -73,7 +73,7 @@ certificates can be generated through `cert-manager`, more information about
7373this project found [ here] ( https://github.com/jetstack/cert-manager ) .
7474
7575Next, populate the OIDC authenticator Secret using the secrets given to you
76- by your OIDC provider in ` ./demo /yaml/secrets.yaml ` . The OIDC provider CA will be
76+ by your OIDC provider in ` ./deploy /yaml/secrets.yaml ` . The OIDC provider CA will be
7777different depending on which provider you are using. The easiest way to obtain
7878the correct certificate bundle is often by opening the providers URL into a
7979browser and fetching them there (typically output by clicking the lock icon on
@@ -85,7 +85,7 @@ your address bar). Google's OIDC provider for example requires CAs from both
8585Apply the secret manifests.
8686
8787```
88- kubectl apply -f ./demo /yaml/secrets.yaml
88+ kubectl apply -f ./deploy /yaml/secrets.yaml
8989```
9090
9191You can restart the ` kube-oidc-proxy ` pod to use these new secrets
0 commit comments