more about the k8s move
This commit is contained in:
parent
b017c7f260
commit
ab3b70f718
1 changed files with 23 additions and 1 deletions
|
@ -75,10 +75,32 @@ amazing build cluster I am just executing
|
|||
|
||||
make
|
||||
|
||||
On my notebook and everything else is built & triggered and
|
||||
on my notebook and everything else is built & triggered and
|
||||
uploaded.
|
||||
|
||||
If you can read this, my build was successful and this website is now
|
||||
running in kubernetes.
|
||||
|
||||
## Garbage collection & improvements
|
||||
|
||||
One of the issues of building images over and over again for a website
|
||||
is that there can be a lot of cruft. As we are using an internal
|
||||
[harbor](https://goharbor.io/) instance that runs IPv6 only to host
|
||||
our images, at some point the storage would run out if ... we did not
|
||||
specifiy a policy for automatic image deletion. In case of this
|
||||
website, the last 5 images are kept and when more exists, on a weeky
|
||||
basis pruned.
|
||||
|
||||
One drawback of the current build is that the ikiwiki run takes about
|
||||
2 minutes and depending on my connection the image push might also
|
||||
take about 2 minutes and then argocd waits maybe 5 minutes until it
|
||||
updates the app itself, thus resulting into about 10 minutes delay
|
||||
between start of build until a new version is online.
|
||||
|
||||
As this website is not that frequently updated this does not pose a
|
||||
real problem, but maybe you will read about some improvements here in
|
||||
the future.
|
||||
|
||||
That said - happy hacking and enjoy your day.
|
||||
|
||||
[[!tag ikiwiki kubernetes]]
|
||||
|
|
Loading…
Reference in a new issue