The general mechanism to rollout minor updates will cover cinder's API, Backup, and Scheduler services.

It will also cover the cinder volume service when it's using the standard container, but it will not cover the custom vendor volume container in a nice way. It will basically just have a mechanism to exclude the service from being managed by the new OpenStackVersion controller.

This card is to work a nicer mechanism than excluding it from the OpenStackVersion object and then having to patch the OpenStackControlPlane object with the specific custom image containers for the cinder volume backends.

Ideally we would be able to define the images in the OpenStackVersion object directly. That way when we change the version to be updated in the object we would also see that we have the cinder volume images to be updated.