Rebuild images for supported product versions on a regular basis
ianpittwood opened this issue · comments
Currently, once a new version of a product is released, we no longer build additional images for previous versions. Letting the previous versions of these images go stale could open them up to newly discovered vulnerabilities while they're still in use by customers. Unfortunately due to the way our workflows are currently structured, it is also very difficult for us to go back and make patches on previous versions. To fix this issue, we should modify our workflows to rebuild images with the latest security updates on a regular schedule to ensure customers are receiving images that are as secure as possible even if they aren't using the latest supported version.
Ideas:
- Git repo Tag supported product versions to make them easier to target for rebuilds (e.g.
connect/2023.01.0). - Decide on a cadence for rebuilds (2 weeks?)
- Decide on whether to push rebuilds to existing tags or extend tag with a build number or date