kubeconfig file is not being generated during Tinkerbell Demo

[ghostheory]

Description

The kubeconfig file I am assuming is supposed to be generated at time of Terraform's provisioning is not there (as per your documentation on the Lokomotive TInkerbell Quick Start page). Instead I am seeing:

WARN[0020] Kubeconfig file not found in assets directory, pulling kubeconfig from Terraform state, this might be slow. Run 'lokoctl cluster apply' to fix it.  args="[]" command="lokoctl cluster apply"

and then:

FATA[0024] Applying cluster failed: getting kubeconfig: reading kubeconfig file content from Terraform state: failed getting Terraform output for key "kubeconfig": executing with arguments 'output, -json, kubeconfig': exit status 1  args="[]" command="lokoctl cluster apply"

Impact

I can't test your project. Will probably move on if I can't fix this in the next few days.

Environment and steps to reproduce

1. Set-up: Baremetal server running Ubuntu 18.01, followed your guide as found in https://kinvolk.io/docs/lokomotive/latest/quickstarts/tinkerbell/ spec'ing out the requirements (the Terraform and Terraform libvirt plugin were especially cumbersome since you are requiring old versions of both to just get your lokoctl apply to run).
2. Task: running lokoctl cluster apply -v to get the cluster up and running
3. Action(s): running lokoctl cluster apply -v to get the cluster up and running
4. Error: FATA[0023] Applying cluster failed: getting kubeconfig: reading kubeconfig file content from Terraform state: failed getting Terraform output for key "kubeconfig": executing with arguments 'output, -json, kubeconfig': exit status 1 args="[]" command="lokoctl cluster apply"

Expected behavior

I expected the automagical provisioning of a lokomotive/k8's cluster on flatcar os VM's to be completed. Wondering if thi is Tinkerbell/libvirt specific issue, or something to do with Terraform (or your code?)?

Additional information

¯_(ツ)_/¯