From 7bdf742e818185d2ccde7850e8fd182d86b5cd0f Mon Sep 17 00:00:00 2001
From: justusbunsi <justusbunsi@noreply.gitea.io>
Date: Mon, 14 Feb 2022 16:00:47 +0800
Subject: [PATCH] Add example for Kubernetes secret as additional source (#294)

As discussed in #286, an example for using Kubernetes secrets as additional configuration source was missing. This adds it.

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/294
Reviewed-by: techknowlogick <techknowlogick@gitea.io>
Reviewed-by: luhahn <luhahn@noreply.gitea.io>
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io>
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io>
---
 README.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/README.md b/README.md
index 7c7d7bd..303679b 100644
--- a/README.md
+++ b/README.md
@@ -341,6 +341,21 @@ data:
     ENABLED=true
 ```
 
+Or when using a Kubernetes secret, having the same data structure:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+  name: gitea-security-related-configuration
+type: Opaque
+stringData:
+  security: |
+    PASSWORD_COMPLEXITY=off
+  session: |
+    SAME_SITE=strict
+```
+
 ### External Database
 
 An external Database can be used instead of builtIn PostgreSQL or MySQL.