Update k3d creation to use the Terraform provider

[fharper]

What is your feature idea?

Update k3d creation to use the Terraform provider so its functioning like any other cloud, but even more important, it will be easier for an user to change the number of agents, and the memory allocation for each of those directly from the gitops-template.

Why is it needed?

When we added the local feature, we decided that due to the ephemeral state of a local cluster and the localhost experience, that the creation, and deletion by the k3d CLI would be safer and more reliable than using the Terraform provider. So for one to change the memory allocation (or the number of agents), it needs to be done by modifying this line in the runtime. The user will need to run the CLI from a fork, pointing to the runtime fork package.

It is not possible to do so by modifying the gitops-template repository like for any other cloud supported.

Is this missing feature preventing you from using kubefirst?

• Yes

Code of Conduct

• I agree to follow this project's Code of Conduct

[fharper]

This need to be discussed with the team as we had reasons to not use the Terraform provider. I think it's because it was causing issues when destroying a cluster that was not successfully created, because of our needs for the state storage. I don't have more information on that as it's been a while, we would need to do other tests.

If it's not possible to use the k3d Terraform provider for whatever reason, it should then be created as flag options for the k3d create command.