@stackflag.bsky.socialCVE-2026-77459 - argo-cd
If you use Argo CD version 2.10.0 through 3.3.15, 3.4.10, 3.5.4, or 3.6.0‑rc2, a delete operation can bypass the normal checks that stop it from creating objects in forbidden…
Too many irrelevant or confusing CVEs? Use stackflag.com
@robrich.bsky.socialwww.linkedin.com/posts/devops... - A cool infographic about #ArgoCD
@saaro.net📝 Neuer Blog-Beitrag: Argo Rollouts 2026: Progressive Delivery als Standard im GitOps-Stack
Canary- und Blue-Green-Releases, automatisierte Analyse und v1.10.0: Wie Argo Rollouts Releases auf Kubernetes messbar und sicher macht – und wo es sich von Flagger un…
@akuity.ioICYMI: self-service deploys without giving up the audit trail. 🎥
See Kargo promotion guardrails, Deployment Advisor, and the On-Call Agent working together across dev → staging → prod. 🔁
Watch: buff.ly/I2I6vnn
@detoxima2025.bsky.social
@darryl-ruggles.cloud#GitOps #ArgoCD #Terraform #Kubernetes #EKS
Terraform gives you a cluster you can stand behind, but it's difficult to keep your Terraform state in sync with the real deployed resources. Patches get pushed, people hot-fix issues, and suddenly you are no longer aligned. It
@akuity.ioTerraform provisions. Argo CD deploys. 🐙
But where should Terraform-generated deployment config live?
Our refreshed guide compares the GitOps Bridge with a Git-based workflow for Helm + Kustomize.
@hugovalters.bsky.socialYour CI holds cluster-admin and runs kubectl apply. ArgoCD flips it: pull, not push, so a compromised runner can't touch prod. Here's how.
https://www.valtersit.com/guides/gitlab/gitops_and_argocd-why_you_should_stop_pushing_your_deployments/
#gitops #argocd #kubernetes
@securityonline.bsky.socialFour critical Argo CD vulnerabilities, including AppProject bypass CVE-2026-77459, threaten the repo-server and clusters. Upgrade to v3.5.4 now.
#ArgoCD #Kubernetes #GitOps #CVE202677459 #Kustomize #Jsonnet #DevSecOps #Vulnerability
@akuity.ioICYMI: Kargo promotes. Argo CD deploys. 🐙
Taylor Thomas walks through where Kargo fits between CI and CD, then demos dev → staging → prod with verification, approval gates, and rollback. 🔁
Watch: buff.ly/1icv3mO
@akuity.ioHappening today! 🎥
Learn how Kargo works with Argo CD to manage promotions across dev → staging → production.
Kargo Maintainer Taylor Thomas walks through the fundamentals at 8AM PT / 11AM ET.
Register: buff.ly/xxvgf0k
@argoproj.io🚀 ArgoCon North America 2026 is coming to KubeCon + CloudNativeCon NA!
What can you expect?
Your Co-chairs, Dan, Christian, and Katie put together a preview of what’s ahead 👇
See you in Salt Lake City! 🏔️
@akuity.ioNew to Kargo? Start here. 👋
Tomorrow, Kargo Maintainer Taylor Thomas covers how Kargo works with Argo CD and brings structure to promotions across dev, staging, and prod.
Register: buff.ly/xxvgf0k
@hugovalters.bsky.socialGitOps and ArgoCD: Stop Pushing Deployments — hands-on guide for sysadmins. #gitops #argocd #kubernetes
@saaro.net📝 Neuer Blog-Beitrag: Argo CD 3.5: Interne mTLS, Source Integrity und die neue ApplicationSet-UI
Argo CD 3.5 (GA August 2026) bringt interne mTLS für die repo-server-Kommunikation, Git-Commit-Signaturprüfung per Source Integrity und eine native ApplicationSet-U…
@qiita-trending.bot.chrs.toArgo RolloutsのBlue-Greenは「2つの環境の交代」じゃなかった ― 名前に引きずられて誤解していた話
@qiita-trending.bot.chrs.to個人開発でApp Storeリリースフローを学ぶ（三部作）― 本番だけ静かに壊れた、CI/CDの2つの事故
@akuity.ioThe September edition of The GitOps Monthly is here! 🐙
AI agents + GitOps, Kargo promotion, Argo CD 3.6 RC1, Terraform workflows, DORA metrics & upcoming live demos.
Catch up here: buff.ly/U3cKprA
@akuity.ioA successful Argo CD sync is not the end of the delivery workflow. 🐙
Kargo helps manage what moves next across dev, staging, and production.
Learn the basics with Kargo Maintainer Taylor Thomas:
@curiousdevscorner.bsky.socialKubernetes Rolling Updates vs. Progressive Delivery with Argo Rollouts medium.com/curious-devs...
#kubernetes #argocd #argorollouts #devops