sheppy/opendesk
1
0
Fork 0
mirror of https://gitlab.opencode.de/bmi/opendesk/deployment/opendesk.git synced 2025-12-06 15:31:38 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs(gitops.md): [#206] Add warning about secrets in pre-rendered yaml files

Browse Source
This commit is contained in:
Thorsten Roßner
2025-11-18 09:40:04 +01:00
parent 080073119b
commit a83ecd5c01
2 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.gitlab-ci.yml
View File

@@ -4,7 +4,7 @@
--- ---
include: include:
- project: "${PROJECT_PATH_GITLAB_CONFIG_TOOLING}" - project: "${PROJECT_PATH_GITLAB_CONFIG_TOOLING}"
ref: "v2.4.10" ref: "v2.4.17"
file: file:
- "ci/common/lint.yml" - "ci/common/lint.yml"
- "ci/release-automation/semantic-release.yml" - "ci/release-automation/semantic-release.yml"

5
docs/enhanced-configuration/gitops.md
View File

@@ -31,6 +31,11 @@ There are two options to deploy openDesk via Argo CD described in the following
## Option 1: Use YAML manifests ## Option 1: Use YAML manifests
> [!warning]
> Pre-rendering the YAML files will also embed all referenced secrets into the resulting outputs.
> You must ensure that these files are accessible solely to individuals who are expressly authorized
> to view the corresponding secrets, as well as the infrastructure and data protected by them.
This option requires a preprocessing step before using Argo CD. This step requires you to compile the Helmfile based This option requires a preprocessing step before using Argo CD. This step requires you to compile the Helmfile based
deployment into Kubernetes YAML manifest, to do so you need to execute the helmfile binary: deployment into Kubernetes YAML manifest, to do so you need to execute the helmfile binary: