That took a lot of work but I'm happy with my progress: I got woodpecker CI to work with forgejo - both running on my #homelab with #kubernetes! Also, argoCD has been in charge of deploying some of my self hosted apps now. Next step will be to learn how to handle secrets within helm and argoCD. #devops

Of course I have some notes of all that debugging and setup that I'll turn into a post soon :) Sleep first!

@electret nice, I‘m currently also experimenting with #k3s controlled through #ArgoCD with a self hosted #Forgejo. #renovatebot updates the helm chart of the #appOfApps each night and creates pull requests which gets validated by a #forgejorunner worklow before merging. Still at the beginning of the journey from single host docker to a cluster though.
@ChrisRichner sounds great! How do you like forgejo runner?

@electret it took me a while to get the setup right. So far so good, I'm able to build and push my own container images that I can reuse as job container images to do argocd apps validation for instance.

Renovate does a good job keeping all those workflows and Dockerfiles up to date.

A nice setup, but a lot of hours wrapping my head around the concepts and configs to finally make it work.

Do you have any runners as well?

@ChrisRichner I just managed to get woodpecker to build images here :) I'm not sure how much I like it. It's definitely a simple tool as far as runners goes, but maybe not best suited for k8s.
My goal now that I can build images is to get the full flow working, I'll evaluate other runners later (forgejo runner & argo workflow are prime candidates).
@electret great, it get's never boring in the #HomeLab right :) I used to have a simple list with things I plan to do in #docmost but nowadays started to use Issues in #forgejo. So #forgejo is now really the single source of truth in the homelab with all the glory #git delivers.