3 ms·
No, I know what Ansible is, thanks. I've written and maintained Ansible playbooks. I respect myself, my team, and my customers and deploy statelessly with NixOS
by k8svet 3y ago
No, I know what Ansible is, thanks. I've written and maintained Ansible playbooks. I respect myself, my team, and my customers and deploy statelessly with NixOS. My life is significantly easier than it was in the salt/Ansible days and there's no amount of money worth those headaches.
> It's yet another layer of yaml to throw at the declaration problem.
Really, my head is already starting to hurt. I KNOW.
> This was just enough for me to post... they aren't mutually exclusive.
I'm sorry but there's no fucking good reason to templatize k8s yaml into Jinja/Ansible. Just hell no. Just more Ansible Things that look like a solution because folks don't actually know k8s.
- bravetraveler 3y agoThis whole thing is based on a perceived false dichotomy of Ansible/K8s I'm not saying using Ansible for K8s is necessarily a good idea, just that laughing because it's mentioned in the same neighborhood is hardly reasonable I'd gladly use it for node-level tasks, for example - in the cluster I'd be less excited. Custom facts are neat. The module library is neat. Possibilities are too, dismissive nature isn't