From da8a4dc3d3ebc5b1621fa45d5f908a96fff56984 Mon Sep 17 00:00:00 2001
From: Lun-Kai Hsu <lunkai@google.com>
Date: Mon, 4 Feb 2019 18:51:45 -0800
Subject: [PATCH] Add step to setup secret in test infra setup (#302)

---
 README.md | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 14a1bcf60aa..fc417e4eb76 100644
--- a/README.md
+++ b/README.md
@@ -486,7 +486,19 @@ Create the PVs corresponding to external NFS
 ks apply ${ENV} -c nfs-external
 ```
 
-#### Troubleshooting
+### Creating secret for deployapp test
+
+The e2e test that runs click-to-deploy app will test deploying kubeflow to a cluter
+under project kubeflow-ci-deployment.
+So it needs to know a clientID and secret of that project.
+Check out this [page](https://pantheon.corp.google.com/apis/credentials?project=kubeflow-ci-deployment&folder&organizationId=714441643818)
+and look for client ID called deployapp-test-client.
+
+```
+kubectl create secret generic --namespace=${NAMESPACE} kubeflow-oauth --from-literal=client_id=${CLIENT_ID} --from-literal=client_secret=${CLIENT_SECRET}
+```
+
+### Troubleshooting
 
 User or service account deploying the test infrastructure needs sufficient permissions to create the roles that are created as part deploying the test infrastructure. So you may need to run the following command before using ksonnet to deploy the test infrastructure.