Open Jackbennett opened 1 year ago
It's complicated, as images are pulled by Talos and CRI.
Talos applies any changes on the fly.
CRI applies some changes on the fly, and some not. CRI should be fixed eventually to support reloading everything on the fly, but it's not something we have control over.
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
It's not stale but unresolved. Making the cri dynamic works sure be cool but I think this issue is more about the manual knows a key needs a reboot so the cli could let me know ones needed. Or if not at apply time some reconcile earning, like you get if I use mismatched talosctl versions
Feature Request
Updated machine registry config requires a reboot, but the cli does not warn you;
Kind of implies to me there's a check if a reboot might be required on apply.
Description
Within the manual;
So upon applying that change the CLI could know it won't take effect until reboot. I think not automatically rolling out reboots is the correct behaviour.