badhouseplants/badhouseplants-net-old
Archived
4
0
Fork 0
Code Issues 7 Pull Requests 2 Actions Packages Projects Releases Activity

update helm chart to support drafts

Browse Source
This commit is contained in:
Nikolai Rodionov
2023-02-25 18:06:56 +01:00
parent b9733a6a21
commit 1f106860ff
4 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/posts/argocd-dynamic-environment-per-branch-part-1/index.md
View File

@ -40,7 +40,7 @@ Before I can start deploying them, I have to prepare the application for that. A
1. Container must not contain any static content
2. I can't use only latest tags anymore
3. Helm chart has a lot of stuff that's hardcoded
4. CI pipelines must be rewritten almost completely
4. CI pipelines must be adjusted
5. Deployment process should be rethought
### Static Container
@ -142,6 +142,7 @@ I had to find all the values, that should be different between different environ
1. Istio `VirtualServices` hostnames (Or Ingress hostname, if you don't use Istio)
2. Image tag for the container with the source code
3. And a hostname that should be passed to hugo as a base URL
4. Preview environments should display pages that are still `drafts`
So all of that I've put to `values.yaml`
```YAML
@ -152,6 +153,7 @@ istio:
image:
tag: $COMMIT_SHA
baseURL: https://badhouseplants.net/
buildDrafts: false
```
### CI pipelines
@ -178,4 +180,6 @@ Now I need to push a new image on each commit instead of pushing only once the c
from_secret: GITEA_TOKEN
repo: git.badhouseplants.net/allanger/badhouseplants-net
tags: ${DRONE_COMMIT_SHA}
```
```
Now if my code is not really broken, I'll have an image for each commit. And when I merge my branch to `main` I can use a tag from the latest preview build on for the production instance. So I'm almost sure that what I've tested before is what a visitor will see.