-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide some sort of cloud-config
for upgrades
#849
Comments
I wondered about this use case too, so I'll drop some input. My understanding was that the new config should not override the existing ones (for example from the registration). We already have the What I think the request wanted was to Still this enters the configuration changes scenario, so my argument as usual is to use the reset flow instead. Edit: Nevermind this entire comment. The |
Indeed, Also note this feature is also leading us to the need of snapshotting |
The idea would be having a mechanism to define some
cloud-config
for the upgrade. This is relevant in cases where thecloud-config
initially provided in the MachineRegistration is no longer valid or incomplete after the upgrade. In such cases it would be handy having the availability to apply some additionalcloud-config
that is honored on next reboot after the upgrade or even applied during the upgrade via upgrade hooks.Consider something like setting a
cloud-config
in ManagedOSImage resource that is converted in to a yaml file that gets dropped in node's/oem
partition before starting theelemental upgrade
call, this way even upgrade hooks could be an option.The text was updated successfully, but these errors were encountered: