It took a couple of weeks learning how the the values yaml files for rook ceph are supposed to be written. But I have finally managed to get a rook ceph storage cluster configured on a Talos kubernetes cluster!
I can do this stuff!
Next step is getting it to work with an ArgoCD CI/CD pipeline.
Just a big shoutout to #Ansible and #AWX for being able to manage a AWX instance using Ansible.
The instance is running in #Kubernetes, managed by #ArgoCD. But the inner configuration of AWX (LDAP, Teams, Organisations, Permissions, Templates, Projects, Inventories, Credentials) needs to be managed,too. That is where Ansible comes in.
Next week I will once again have a AWX instance that manages itself by running a job on AWX. Nice, eh?
Interesting piece on the details of actual scale and shifting from Helm to CueLang with ArgoCD. Includes the why's as well as lessons learned.
The Art of #ArgoCD ApplicationSet Generators with #Kubernetes
https://piotrminkowski.com/2025/03/20/the-art-of-argo-cd-applicationset-generators-with-kubernetes/
Check out the new #GitOps capabilities of the @microcksio #Kubernetes Operator!
Create rich and reproducible sandbox environments fully declaratively with #ArgoCD. Manage the content just by pushing changes to a Git repo 
Another gorgeous playlist to soundtrack my day.
Matches my mood. Had an interview this morning after 4 hours of sleep due to my sick daughter being up half the night. Went well til they started asking about Kubernetes/Helm/ArgoCD type question. Felt awful, hopefully the rest of the interview went well enough. We'll see.
What I did in the last weeks (part 2):
All of my k3s clusters (and I have a few of them for $REASONS) are now running either #fluxCD or #argoCD. So everything #gitops now.
In general, I like the lightweightness of fluxCD, not having to run Redis and whatnot. But having a GUI is sometimes nice, even though the flux CLI is really easy to use and very intuitive.
And of course, #renovatebot is watching all repositories and sending merge requests to update things in the clusters. Nice!
@heywoodlh @farcaller I hope I'm not overstepping but you might also be interested in nixidy which takes a different approach of using nix with ArgoCD. Instead of using a config management plugin to render manifests with nix, I use CI to render them and commit them back to my repo for ArgoCd to pick up.
Full disclosure: the project is mine but I build on some of farcaller's work.
@heywoodlh it is a bit of a mess, sorry for that!
It will, by default `nix build .#kubernetesConfiguration`. You can modify that in 3 ways:
1. In your Application resource, you can specify spec.source.plugin.env['NIX_OUTPUT']=customOutput. That allows you to build flakes from something other than kubernetesConfiguration.
2. In spec.sourpce.plugin.parameters["IMPURE"] you can set it to `true` to build with --impure (I use that to load flakes from other flakes in the same master git repo by relative path)
3. spec.sourpce.plugin.parameters["VALUES"] you can specify a literal josn string taht will be expanded into values.json. Then, in your flake, you can read ./values.json. A poor man's flake config!
With all that in mind, you *want* to have one Application per one flake output if you have several apps in your repo so that you can manage their states in argocd individually. I figured I just prefer multiple flake files with a single output.
Want to see Argo Rollouts in action? 
I wrote a hands-on guide for the CNCF blog, showing how to automate a canary deployment on Kubernetes with:
☆ Argo Rollouts
☆ Istio
☆ Prometheus
Follow along, deploy safely, and watch your rollout in real-time!
Read it here:
https://tinyurl.com/ArgoRollouts
Стратегии деплоя: как мы пришли к использованию Argo CD
Привет, Хабр! Меня зовут Егор Салиев, я DevOps-инженер в провайдере IT-решений Hilbert Team. Сегодня хочу затронуть тему, которую недавно обсуждали на Kuber MeetUp в Selectel, и которая будет интересна инженерам, занимающимся настройкой CI/CD и деплоем. Рассмотрим, как со временем менялась практика развертывания приложений в Kubernetes. Обсудим переход от ручного процесса к автоматизации и сравним две модели деплоя: push и pull. В результате мы дойдем до современного подхода — GitOps с Argo CD. Такой метод помогает компаниям стандартизировать процессы, уменьшить количество ошибок и сбоев, ускорить вывод продукта на рынок, а также сократить расходы на инфраструктуру.
Do you know how to define release pipelines? Have experience in building environments from developer sandboxes to production? Then you're the right person to talk at DevConf.CZ 2025!
Any tools and best practices in #DevOps and #Automation, agile development practices, continous application development or testing strategies are welcome!
Submit your proposal now at https://pretalx.devconf.info/devconf-cz-2025/cfp
#Ansible, #AIOps, #CI/CD, #Tekton, #ArgoCD, #SiteReliabilityEngineering
wew new #ArgoCD and #cloudflared tunnel for the #AREDN connected #RaspberryPi 5 
still a lot more to do but this has been on my agenda for waaaaaay too long.
#ArgoCD ApplicationSet generators currently baking my noodle. This is a really big gun I can wave around and hopefully not blow anyone's feet off.
Find myself needing to learn about #Openshift and #argocd wondering how people pre-approve operator installs in #IAC / #Automation with a specific version without setting the entire operator to update automatically (This will cause a conflict between desired version and what gets installed). Getting rid of the manual step to approve is the goal here.
Creating an installPlan manually with install approved doesn’t seem to work since the operator creates its own installPlan that overrides it.
Tomorrow on 'You Choose!', Viktor Farcic and I will discuss Policies and State Synchronization with Kyverno and Argo CD—CNCF tools you’ve already chosen in past seasons. ♫
Join us as we continue building an Internal Developer Platform!
fun fun fun
Don’t miss it! Click ‘Notify Me’:
#k8s journey continues:
Got #ArgoCD up and running and then followed this really helpful guide (https://christianhuth.de/deploying-helm-charts-through-argocd-streamlining-kubernetes-deployments/#3-argocd-application-pointing-to-a-helm-dependency-in-a-git-repository) to try out my first Argo application to stand up #openwebui and it all went extremely smoothly!
Swapping #Flux2 for #ArgoCD, #Kustomize for #Helm. I see what I'm gaining but it's rough starting more or less from knowing nothing. #kubernetes
Today’s episode: 'Branching Realities'
I’ve set up #ArgoCD to manage multiple environments, each tied to a different branch in the repo. This learning experience keeps getting deeper and wider—like falling into a Kubernetes-shaped black hole.
Anyone got solid zero to hero #Kubernetes courses to recommend? I could use some structured wisdom before YAML consumes my soul.
More adventures under #SelfHostingChronicles.
arc) 
