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

Move all pictures to LFS

Browse Source
This commit is contained in:
Nikolai Rodionov
2023-04-25 10:34:03 +02:00
parent b5e304bc3c
commit fdbf6c4636
22 changed files with 34 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
content/posts/argocd-dynamic-environment-per-branch-part-1/cover.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 7.6 MiB

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

@ -4,7 +4,7 @@ date: 2023-02-25T14:00:00+01:00
draft: false
ShowToc: true
cover:
image: "cover.png"
image: "/posts/argocd-dynamic-environment-per-branch-part-1/cover.png"
caption: "Dynamic Environment Per Branch with ArgoCD"
relative: false
responsiveImages: false
@ -98,7 +98,7 @@ containers:
name: nginx-config
```
So in the `init` container I'm generating a static content (`--baseUrL` flag is templated with `Helm`). Putting the result to the directory that is mounted as en `emptyDir` volume. And then later I'm mounting this folder to a container with `nginx`. Now I can use my docker image wherever I'd like with the same result It doesn't depend on the hostmame that was fixed during the build.
So in the `init` container I'm generating a static content (`--baseUrL` flag is templated with `Helm`). Putting the result to the directory that is mounted as en `emptyDir` volume. And then later I'm mounting this folder to a container with `nginx`. Now I can use my docker image wherever I'd like with the same result It doesn't depend on the hostname that was fixed during the build.
### No more `latest`
Since I want to have my envs updated on each commit, I can't push only `latest` anymore. So I've decided to use `commit sha` as tags for my images. But it means that I'll have a lot of them now and having `300Mb` of images and other media is becoming very painful. That means that I need to stop putting images directly to container during the build. So instead of using `rclone` to get data from `minio` in a `drone` pipeline, I'm adding another `init` container to my deployment.
@ -481,7 +481,7 @@ foreach my $line (@builds_out)
```
{{< /details >}}
It's far from being perfect, but it works and I like that I was able to finally use `Perl` somewhere
It's far from being perfect, but it works, and I like that I was able to finally use `Perl` somewhere
2. I want to have a manifest that I can apply in case of kind of *disaster recovery*. And it means that `ApplicationSet` should contain enough information to deploy a production instance of my blog right off the bat. But I don't want to keep it up-to-date with every new commit hash. So I've decided to keep pushing `latest` to registry but only on `main` builds. So I can use the latest tag in application set, but in the application life-time I'll keep using `SHA` as tags. The only static hard-coded value in the `ApplicationSet` is a version of the `Helm chart`. And I don't know how to automate it yet. But I'm sure that I will do it somehow.
I know that it's a very common practice to store all `Argo` resource in `git`. But I don't see any sense in storing manifests for temporary environments that can be recreated by clicking a button in `Drone` or by pushing a new commit.