Memoize SeedImage building

[agracey]

Currently, if I go to the UI and click "Build ISO" a new SeedImage gets created. If I keep clicking this button, I end up with a bunch of pods all hosting the same thing.

Would it make more sense to add some labels/annotations to that SeedImage CR then match the requested config to allow for reuse?

[fgiudici]

We somehow already do something that could be useful on the backend side: we have annotations tracking the base image, the referenced registration and the cloud init that would allow us to know if we should re-build the ISO or not on SeedImage update.
So, on the UI side keeping the same name for the seedimage (overwriting it if already present) may work 🤔
( CC @aalves08 )

[agracey]

Could we move this to the ui repo? (I don't have the correct permissions)

[aalves08]

Issue moved @agracey . I've asked for permissions to add the elemental group to the elemental-ui repo so that you could do this kind of operation (I don't have enough permissions to do that). 🙏

[aalves08]

We somehow already do something that could be useful on the backend side: we have annotations tracking the base image, the referenced registration and the cloud init that would allow us to know if we should re-build the ISO or not on SeedImage update. So, on the UI side keeping the same name for the seedimage (overwriting it if already present) may work 🤔 ( CC @aalves08 )

I'll have to check if that will work. Thanks for the input @fgiudici 🙏

[aalves08]

@fgiudici does this issue make sense still? doing a bit of backlog grooming

[fgiudici]

Well, the issue is still there: anyway, it is not a critical one, it is "just" annoying as you may have to go around and delete old SeedImage resources created by the UI.
So, from my PoV: yes, the issue still makes sense but is pretty low on priority.