volsync icon indicating copy to clipboard operation
volsync copied to clipboard

Unified container image

Open JohnStrunk opened this issue 3 years ago • 0 comments

Describe the feature you'd like to have. Right now, we build several containers that must all be used together:

  • Volsync operator
  • restic mover
  • rclone mover
  • rsync/ssh mover
  • syncthing mover

All 5 of these final images are based on the same base (ubi9-minimal). We should consider building a single image that contains all the components.

What is the value to the end user? (why is it a priority?)

  • Users need to be careful to use the same release across all container images
  • Users in offline environments must mirror them all separately
  • With a single image, it is more likely that it would already be present on a node

How will we know we have a good solution? (acceptance criteria)

  • [ ] All components reside in a single container image
  • [ ] Invoking a mover or the operator is just a matter of using a different entrypoint in the container
  • [ ] Helm chart should ensure the same image is used for all components

Additional context A quick test of putting everything into a single container indicates we'll end up w/ 1 image of about 718 MB. The bulk of this is due to the rsync/ssh mover (522 MB standalone). The current sum of the separate containers is 1213 MB.

JohnStrunk avatar Sep 23 '22 15:09 JohnStrunk