Yeah I do agree regarding putting everything in manifests , but then i will need to wait for the resources to be deployed, and that is what I am trying to avoid. Like save the waiting time needed to deploy the k8s resources.
Regarding the CAs , that is fine. Because this VM will be up for 5 minutes in the CI pipeline , run the tests and then deleted.
There will be a builder vm that build the iso every night ( nightly)
But my question was more focused on what paths I should include in the iso builder scripts that k3s uses
For example you mentioned /var/lib/rancher/k3s
Where can I find all paths that k3s uses?