A k3s cluster can begin as a quick experiment: one server, a curl command, and a kubeconfig copied to a laptop. That is useful for learning, but it does not scale into a dependable platform. The moment a cluster runs shared services, hosts internal applications, or becomes part of a delivery pipeline, its creation needs to be repeatable.
The practical division of responsibility is simple:
Terraform creates the infrastructure: virtual machines, networks, IP assignments, DNS records, and firewall rules.
Ansible configures those machines: operating-system prerequisites, k3s installation, node joins, kubeconfig handling, and post-install validation.
k3s provides the lightweight Kubernetes distribution that runs the workload.
This combination turns cluster provisioning from a sequence of terminal commands into a versioned, reviewable system.…