Closed sirishkr closed 2 months ago
Kubeconfig as an output to cloud space resource will be difficult to implement because the kubeconfig does not become immediately available after cloudspace creation. It becomes available after control plane becomes ready.
The spot_kubeconfig
data source with id = name of cloudspace
should output the kubeconfig.
See discussion here: https://www.reddit.com/r/rxt_spot/comments/1bp8cf5/billing_questions_are_we_paying_for_unusable_nodes/
Multiple users requesting it:
I very much want that. The kubeconfig as an output of the cloudspace resource would be great.
Also, the ability to fetch/refresh the Terraform token would be nice. When it times out and rotates, it breaks me until I manually refresh it in my automation.