Currently, the release controller links to the release browser to offer the RPM diff between two CoreOS versions. This won't work with https://github.com/openshift/enhancements/pull/1637 since the node images will be just like any layered images built in separate pipelines and not by the same tooling.

Really, the tooling necessary here to get the RPM diff should not be unique to the OS container, but we're breaking expectations by breaking the release browser flow to compare rhel-coreos images.

One idea I have here which shouldn't be very hard is to add another container in the release browser (like buckateer), which just watches for new CI (and then eventually prod) node image builds, pulls them down and extracts their rpmdb, converts to commitmeta.json, and uploads to someplace in S3, use the sha256 as its name. Then update the release browser to learn to look in that spot in S3 to retrieve the commitmeta.json files when passed some URL parameter. Then update the release controller to pass that URL parameter when diffing layered images.

Feel free to explore other ideas as part of the work on this ticket.

See also discussions in the enhancement: https://github.com/openshift/enhancements/pull/1637#discussion_r1797358258