#argocd

I've been considering Argo Workflows for my CI/CD jobs lately. It feels better than Forgejo Actions in the following ways:

• I can create workflows with some privileges (like creating user namespaces) without going "--privileged". It is not as "on/off" as it can be with Forgejo Actions, because you can express complex securityContexts;
• the workflows manifests may not be part of the code repository, which squelch a whole world of possible attach vectors;
• secrets can be mounted on the need-to-know basis, per container instead of having all secrets possibly exposed as soon as you have write permissions on the repository and the right to run a pipeline.

Am I missing something?

#devops #ci #argoCD

🤖 Unpatched Argo CD repo-server flaw (no CVE, no fix) allows unauthenticated attackers to achieve RCE and full Kubernetes cluster takeover if they can reach the internal port. Reported by Synacktiv. 🔗 https://thehackernews.com/2026/07/unpatched-argo-cd-repo-server-flaw.html #ArgoCD #Kubernetes #RCE #InfoSec #CyberSec

Tonight's activities included, Resolving an issue with corrupt keys files on #cachyos stopping updates. Resolving an issue with #termix which was timing out on my #k8s and fixing ghis also fixed an issue with the Android app I got #patchmon installed and rolled out security and other patches Tomorrow I need to setup my old #imac (intel) as a #devops server (probably ubuntu 2404 desktop) and install #argocd and see if i can get that to work with my k8s setup.. Oh, and we walked the dog 6km in the morning... Got next week off.. so got some housekeeping to do.. #daveknowstech #selfhosted

In a dick move, I migrated to my new laptop and hadn't pushed my helm charts to #gitea Thankfully via #warp.dev and #gpt5 i was able to rebuild my #helm charts which are now up on gitea and accessible by helm. Tomorrow my intent is to get #argocd installed and see how this #cicd pipeline works #daveknowstech #selfhosted #homelab