I wrote about that particular topic a couple months ago: https://www.ansible.com/blog/how-useful-is-ansible-in-a-cloud-native-kubernetes-environment https://www

I wrote about that particular topic a couple months ago: https://www.ansible.com/blog/how-useful-is-ansible-in-a-cloud-native-kubernetes-environment https://www.ansible.com/blog/how-useful-is-ansible-in-a-clou... The answer is: "it's complicated" — there are still many scenarios (even in a more 'cloud-native-oriented' shop) where you need automation to fill the gaps between more provisioning-focused tools (like Terraform) and more scheduling-focused tools (like Kubernetes). Sometimes it's in application build or deployment scenarios, sometimes it's in stringing together different platforms, and in some cases you could even argue for skipping Dockerfiles entirely and using a tool like Ansible to build containers. A lot of it is highly dependent on your team, your resources, and the amount of application tooling you have that's not 100% cloud-native, serverless, [insert other buzzword-worthy tech here].