From 22edf038c3275b457d54ebca344c32f14f99e462 Mon Sep 17 00:00:00 2001 From: JoshVanL Date: Wed, 6 Nov 2019 14:36:20 +0000 Subject: [PATCH] Move static manifests from demo to deploy Signed-off-by: JoshVanL --- README.md | 8 ++++---- deploy/charts/kube-oidc-proxy/README.md | 2 +- {demo => deploy}/yaml/kube-oidc-proxy.yaml | 0 {demo => deploy}/yaml/secrets.yaml | 0 4 files changed, 5 insertions(+), 5 deletions(-) rename {demo => deploy}/yaml/kube-oidc-proxy.yaml (100%) rename {demo => deploy}/yaml/secrets.yaml (100%) diff --git a/README.md b/README.md index d93923624..e0a352b0a 100644 --- a/README.md +++ b/README.md @@ -40,7 +40,7 @@ Directions on how to deploy OIDC authentication with multi-cluster can be found ### Quickstart -Deployment yamls can be found in `./demo/yaml` and will require configuration to +Deployment yamls can be found in `./deploy/yaml` and will require configuration to an exiting OIDC issuer. 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 the newly created `kube-oidc-proxy` Namespace. ``` -$ kubectl apply -f ./demo/yaml/kube-oidc-proxy.yaml +$ kubectl apply -f ./deploy/yaml/kube-oidc-proxy.yaml $ kubectl get all --namespace kube-oidc-proxy ``` @@ -73,7 +73,7 @@ certificates can be generated through `cert-manager`, more information about this project found [here](https://github.com/jetstack/cert-manager). Next, populate the OIDC authenticator Secret using the secrets given to you -by your OIDC provider in `./demo/yaml/secrets.yaml`. The OIDC provider CA will be +by your OIDC provider in `./deploy/yaml/secrets.yaml`. The OIDC provider CA will be different depending on which provider you are using. The easiest way to obtain the correct certificate bundle is often by opening the providers URL into a 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 Apply the secret manifests. ``` -kubectl apply -f ./demo/yaml/secrets.yaml +kubectl apply -f ./deploy/yaml/secrets.yaml ``` You can restart the `kube-oidc-proxy` pod to use these new secrets diff --git a/deploy/charts/kube-oidc-proxy/README.md b/deploy/charts/kube-oidc-proxy/README.md index 778502fe8..e669d68af 100644 --- a/deploy/charts/kube-oidc-proxy/README.md +++ b/deploy/charts/kube-oidc-proxy/README.md @@ -5,7 +5,7 @@ This helm chart cannot be installed out of the box without providing own configuration. This helm chart is based on example configuration provided in `kube-oidc-proxy` -[repository](https://github.com/jetstack/kube-oidc-proxy/blob/182fa79a7854bd33f3827d89e222e10c57c4aed5/demo/yaml/kube-oidc-proxy.yaml). +[repository](https://github.com/jetstack/kube-oidc-proxy/blob/master/deploy/yaml/kube-oidc-proxy.yaml). Minimal required configuration is `oidc` section of `value.yaml` file. diff --git a/demo/yaml/kube-oidc-proxy.yaml b/deploy/yaml/kube-oidc-proxy.yaml similarity index 100% rename from demo/yaml/kube-oidc-proxy.yaml rename to deploy/yaml/kube-oidc-proxy.yaml diff --git a/demo/yaml/secrets.yaml b/deploy/yaml/secrets.yaml similarity index 100% rename from demo/yaml/secrets.yaml rename to deploy/yaml/secrets.yaml