From 6e075388e974cdcc9dcd93182e1aa44164d7829b Mon Sep 17 00:00:00 2001
From: Andrei Kartashov <a@ioot.xyz>
Date: Mon, 4 Sep 2023 22:14:56 +0700
Subject: [PATCH] readme: add oauth2-proxy into bootstrap instructions

---
 README.rst | 25 +++++++++++++++++++++++--
 1 file changed, 23 insertions(+), 2 deletions(-)

diff --git a/README.rst b/README.rst
index 7f070d8..8532d84 100644
--- a/README.rst
+++ b/README.rst
@@ -95,6 +95,19 @@ ArgoCD bootstrap
     argocd repo add git@github.com:amkartashov/gf-k8s --ssh-private-key-path ~/.ssh/argocd.ioot.xyz
 
 
+* Create new Oauth application <https://github.com/settings/applications/new>:
+
+  * Application name: oauth2.ioot.xyz
+  * Homepage URL: https://oauth2.ioot.xyz
+  * Authorization callback URL: https://oauth2.ioot.xyz/oauth2/callback
+  * Update oauth2-proxy client id, secret and cookie secret:
+
+    .. code-block:: bash
+
+      argocd app set argocd/oauth2-proxy --parameter config.clientID REPLACE
+      argocd app set argocd/oauth2-proxy --parameter config.clientSecret REPLACE
+      argocd app set argocd/oauth2-proxy --parameter config.cookieSecret `pwgen -1 32`
+
 * Create new Oauth application <https://github.com/settings/applications/new>:
 
   * Application name: argocd.ioot.xyz
@@ -117,10 +130,18 @@ Passing Sensitive Parameters in ArgoCD apps
 
 Used methods:
 
-* manually creating K8s secrets (f.e. this way is used to configure repo secret in argocd)
-* manually updating K8s secrets (f.e. this way is used to configure GitHub Oauth App client secret)
+* manually creating K8s secrets
+
+  F.e. this way is used to configure repo secret in argocd.
+
+* manually updating K8s secrets
+
+  F.e. this way is used to configure GitHub Oauth App client secret.
+
 * modifying helm parameters in application
 
+  F.e. this is done for Oauth2 Proxy application.
+
 ArgoCD application types which can be used
 ===============================================================================