(after clicking through context...) There's no amount of money you could pay me to do this with Ansible. Like, you could offer me double my salary, and I'd laugh.
The only answer that makes any sense here is Kubernetes.
The only answer that makes any sense here is Kubernetes.
This reads like a brazen misunderstanding/misrepresentation of Ansible.
Like... imagine the position of Terraform, a Kubernetes darling, and that's it.
I could especially see Ansible being used when not buying toy clusters, but building your own. I don't know how useful CRUD on the objects like deployments would be. Enough to do the job.
Point being, Kubernetes doesn't exclude Ansible in the slightest, whatsoever.
This was just enough for me to post... they aren't mutually exclusive. It's yet another layer of yaml to throw at the declaration problem.
Where/what/how is entirely up to the user. I'll take your money and then move on to the next thing to manage
> 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.
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