Closed myoung34 closed 6 months ago
Can't you just use config patches to set desired values?
This happens behind the scenes. Since its not in my yaml or plan there's nothing to patch unless there's something Im missing
Even if I set the values explicitly to null they arent in the plan and get populated anyway
The PR I linked does not include these and yet its populated regardless during the talos apply-config behind the scenes somehow
You have talos_version
to control the defaults based on Talos version you're generating the machine config for.
You should be still be able to override whatever defaults are with config patches.
Im attempting to migrate my random controlplane + worker config yaml to the terraform provider here
I was able to get a 1:1 match except:
KubePrismSupport always has a value. it defaults to true and I cannot nil it out, so I have to set it to enabled:false, but it keeps the port attribute. The only way to remove it is to use
edit mc
to give me this changeKubePrismSupport: &{ServerEnabled: &false, ServerPort: 7445},
KubePrismSupport: nil,
DiskQuotaSupport always has a value. it defaults to true and I cannot nil it out, so I have to set it to false. The only way to remove it is to use
edit mc
to give me this changeDiskQuotaSupport: &false,
DiskQuotaSupport: nil,
certSANs always includes the VIP. While this is probably fine it gives me very little full control over the values. if i set certSANs in the
config_patches
it always includes the value of my VIP which I did not include in this apply and is not expected. This doesnt actually show up in the terraform diff even though it will be set.