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
For installation it's possible to specify which image should be used using:
install:
source: oci:your_image_here
This works because of the way we parse this key but we don't do anything similar when constructing the ResetSpec.
It's useful to have this option because on public cloud, the system is "installed" by performing an auto-reset. Users can specify the image they want to install by booting any cloud image we push to that provider and setting the image to reset to. This way we don't need to push all possible flavors and such.
Problems with this approach:
The parent image defines the recovery partition size so if the image specified by the user is bigger, it might not fit.
We calculate the rest of the sizes based on the "parent" image but this one we can probably fix when we implement this feature.
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
jimmykarily
changed the title
feat: allow user to specify the image to reset to
feat: allow user to specify the source image consistently (reset,install,upgrade, etc)
Feb 10, 2025
For installation it's possible to specify which image should be used using:
This works because of the way we parse this key but we don't do anything similar when constructing the
ResetSpec
.It's useful to have this option because on public cloud, the system is "installed" by performing an auto-reset. Users can specify the image they want to install by booting any cloud image we push to that provider and setting the image to reset to. This way we don't need to push all possible flavors and such.
Problems with this approach:
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: