The keepalived version in our ipfailover-keepalived image is not specified so it picks up the latest version based upon which RHEL version the build runs.  The errata for keepalived shows that over almost 2 years we've had these three version updates (2.1.5-9, 2.2.4-6, and 2.2.8-3).  Keepalived version updates are tied to RHEL versions:

RHBA-2023:6499	RHEL-9.3.0.GA	12 months ago	keepalived-2.2.8-3.el9
RHBA-2023:2335	RHEL-9.2.0.GA	over 1 year ago	keepalived-2.2.4-6.el9
RHBA-2022:7626	RHEL-8.7.0.GA	almost 2 yrs ago	keepalived-2.1.5-9.el8	

We need to let customers and support know how keepalived is updated so that we can track any failures introduced by updates, and issue release notes with updates.
    

4.18.0 and prior
    

See errata for automated builds.
    

I presume  one can review release builds and see the keepalived version changing over time as builds are run on different RHEL versions, but I'm not 100% sure.
    

We don't always know when the keepalived version changes in our image.
    

Control and keep release notes for when the keepalived version changes in our image.
    

Discussed in Slack thread: https://redhat-internal.slack.com/archives/CB95J6R4N/p1729286621964289
Recently noticed in OCPBUGS-29593.
This might be a maintenance and debuggability issue, not a bug.