To fix this issue, you can manually import the vendor addon into the local Lifecycle Manager repository.
To do this, follow the steps below:
Once the import has finished, you will be able to select the new version of the vendor addon in the cluster image configuration.