Closed FlxPeters closed 2 months ago
yes, that's the intended behavior, maybe we can improve it to generate the client kubeconfig from machine secrets instead of retrieving from the talos api which would return a new one every single time
+1
@frezbo It'd be great if we could make it so that it's a fixed value or at least that it only changes when strictly required.
The only fix would be to convert this to a resource
as opposed to a data_source
due TF provider internals
Given I use the example code for the
talos_cluster_kubeconfig
data source, a new kubeconfig is a returned on every terraform apply.This is not a show-stopper bug, but the data source will change on each run which is a change in the plan.
Is this an intended behavior?