@@ -40,7 +40,7 @@ Directions on how to deploy OIDC authentication with multi-cluster can be found
40
40
41
41
### Quickstart
42
42
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
44
44
an exiting OIDC issuer.
45
45
46
46
This 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
54
54
the newly created ` kube-oidc-proxy ` Namespace.
55
55
56
56
```
57
- $ kubectl apply -f ./demo /yaml/kube-oidc-proxy.yaml
57
+ $ kubectl apply -f ./deploy /yaml/kube-oidc-proxy.yaml
58
58
$ kubectl get all --namespace kube-oidc-proxy
59
59
```
60
60
@@ -73,7 +73,7 @@ certificates can be generated through `cert-manager`, more information about
73
73
this project found [ here] ( https://github.com/jetstack/cert-manager ) .
74
74
75
75
Next, 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
77
77
different depending on which provider you are using. The easiest way to obtain
78
78
the correct certificate bundle is often by opening the providers URL into a
79
79
browser 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
85
85
Apply the secret manifests.
86
86
87
87
```
88
- kubectl apply -f ./demo /yaml/secrets.yaml
88
+ kubectl apply -f ./deploy /yaml/secrets.yaml
89
89
```
90
90
91
91
You can restart the ` kube-oidc-proxy ` pod to use these new secrets
0 commit comments