Building a podcast app that truly empowers instance owners means laying down a robust foundation. We’re shedding our legacy constraints and moving Podverse NG to K3s and ArgoCD. 🏗️
Wrote up some thoughts on where we are currently (a Docker Compose alpha is live!) and our vision for a decentralized, resilient future for podcasting.
Check it out: https://z.suorcd.us/posts/20260328-podverse-ng-k3s/
Cool!! Being personally ghosted by Microshaft's Github is.. liberating, I guess I'm just easy to please.
Now if I could just do the same for work . . :/
Sorry to the projects that I've helped, and may have helped further. Go find yourself better infrastructure partners, that wont subject me, and the community you want and/or need, to potential harm or exploitation.
It's not social coding if it results in exploitation, yours or mine.
Argo CD for GitOps Deployment
Deploy apps to Kubernetes using GitOps. Automate delivery with version-controlled configs.
Had to do a maintenance on Immich, postgres cluster got disconnected from the operator (somehow?) and wouldn't scale past 1 replica anymore...
And we don't like single points of failure here
So first, descheduling the Immich pod, to avoid weird writes between last backup and actual DB shutdown
Triggering a manual backup
Deleting cluster
Recovering cluster from last backup
Woops, the shared library object name got renamed from vectorchord 0.3 to 0.4.3, now it's "vchord.so" instead of "vectors.so"
Quick fix and boom, everything comes back up
Restoring Argo auto sync and the cluster is all back up, distributed and shining
When Backups, DevOps and GitOps come back in a smooth and clear motion ⭐
#postgresql #postgres #cnpg #psql #selfhosted #selfhosting #homelab #k3s #kubernetes #linux #opensource #immich #vectorchord #backup #devops #argocd #gitops
Ce soir, direction Toulon pour le meetup #ToulonDev ! 🚀
On va parler GitOps, et j'ai hâte de retrouver ma ville d'origine pour cette soirée tech 💡
Rendez-vous à 18h30 : https://link.davinkevin.fr/AstroGitOps-ToulonDev-program
Cascading deletion of Argo CD apps using GitOps
I learned to consider always setting the finalizer (resources-finalizer.argocd.argoproj.io) with all Argo CD apps a good practice.
Edit: Exception: root app of apps.
💡 This way, users won't be surprised to find that the resources they wanted to delete keep on running but are no longer tracked in Git or by Argo CD (AKA orphaned).
https://argo-cd.readthedocs.io/en/release-3.2/user-guide/app_deletion/#about-the-deletion-finalizer
Anybody know of an equivalent to the GitHub
api.github.com/user
for Azure DevOps? The closest I can find is
But this requires knowing in advance the users id, rather than just using the auth token to work it out
⚔️ su || cd ⚔️
erstwhile
ChrisRichner
Abhinav
anknfriends
DocYeet 
Kevin Davin
Johannes Schnatterer
Ben Hardill