Provide an option to trigger an image rebuild

[Madhu-1]

When KMM builds the module images, it expects the resulting image registry to be stored in a persistent image registry, However when the image registry is configured with ephemeral storage the registry contents are lost on the registry restart, node drain or registry roll out.

After the registry is recreated, KMM still believes that the image exists and it will try to load/unload the module, This leads to the failures on node, because the image referenced in the Module spec no longer exists.

Most importantly if the kernel module is required for some storage solutions, it would not be possible to have an image registry backed by persistence storage in the clusters.

its nice to have a feature if possible provide an option to re-trigger the image build and push it to the registry again. so that we can work with this kind of clusters.

[yevgeny-shnaidman]

@ybettan this is probably a valuable feature to implement.
We can add a build counter to Build configuration of the Module. This counter will be propagated to the MIC and MBSC objects (Spec and Status). Based on those values, the module reconciler can determine if the rebuild was requested or not, and act accordingly. The same goes for MIC and MBSC controllers: they can detemine if action is required based on the BuildCounter in their respective Specs and Statues

[ybettan]

@ybettan this is probably a valuable feature to implement.
We can add a build counter to Build configuration of the Module. This counter will be propagated to the MIC and MBSC objects (Spec and Status). Based on those values, the module reconciler can determine if the rebuild was requested or not, and act accordingly. The same goes for MIC and MBSC controllers: they can detemine if action is required based on the BuildCounter in their respective Specs and Statues

I agree this is a nice feature to have and not very hard to implement.

[ybettan]

This is currently planned for the next release (2.6)