You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yesterday, I tried installing the CA cert the wrong way, with .machine.files. However, I edited it out with talosctl.exe edit mc and rebooted in order to get the node back online.
I confirmed that the files property was not there before patching it again with only the trustedrootsconfig this time, which ended up failing and the .machine.files appeared once more, even though the patch.yaml file did not have anything to configure this property. It only had the trustedrootsconfig doc.
Now, I was replicating the issue once more and gathering screenshots as evidence, replicating the same steps as done yesterday. Even the patch file is the same since I didn't touch it since yesterday.
Now it works... The trustedrootsconfig document is there and .machine.files is not...
I guess I can close this issue since its resolved, but it is very strange how .machine.files ended up there when I patched only the trustedrootsconfig, but is not happening again now...
Activity
frezbo commentedon Jan 2, 2026
Your machine config has
.machine.filesset which should not be used along with trustedrootsconfigAyluinReymaer commentedon Jan 2, 2026
I have no idea what just happened...
Yesterday, I tried installing the CA cert the wrong way, with
.machine.files. However, I edited it out withtalosctl.exe edit mcand rebooted in order to get the node back online.I confirmed that the files property was not there before patching it again with only the trustedrootsconfig this time, which ended up failing and the
.machine.filesappeared once more, even though the patch.yaml file did not have anything to configure this property. It only had the trustedrootsconfig doc.Now, I was replicating the issue once more and gathering screenshots as evidence, replicating the same steps as done yesterday. Even the patch file is the same since I didn't touch it since yesterday.
Now it works... The trustedrootsconfig document is there and
.machine.filesis not...I guess I can close this issue since its resolved, but it is very strange how
.machine.filesended up there when I patched only the trustedrootsconfig, but is not happening again now...