We need to investigate what the changes to Keycloak (RH-SSO) mean to 3scale and ensure the supportability continues without interruption for customers.

More details from the PM's announcement: 

Red Hat Single Sign-On (RH-SSO) version 7.6 is the last planned minor update release in the RH-SSO 7.x family, which now enters the maintenance phase of its lifecycle. The RH-SSO 7.x lifecycle [5] has been extended with maintenance support now ending on June 30th 2025.

In the community, we are progressing a Keycloak.X initiative aiming to introduce a number of significant changes to make Keycloak leaner, easier and more future-proof. We’re switching to Quarkus as the platform used to build Keycloak. Quarkus, being a Java and Container-First stack, provides a more natural path for bringing all the capabilities and requirements for running in a more cloud-native fashion to Keycloak, with a focus on platforms such as Kubernetes and Openshift. With this Keycloak.X new distribution powered by Quarkus, we are aiming to provide a reduced startup time, lower memory footprint, container-first approach, better developer experience, all with a strong focus on usability, scalability, and optimized for running in the hybrid cloud.

Considering these larger changes in the Keycloak architecture and to fully leverage the power of the Keycloak brand while also aligning with the Red Hat build of Quarkus lifecycle, we have decided to rename Red Hat Single Sign-On to Red Hat build of Keycloak, starting with what will be the next major release of Red Hat Single Sign-On (RH-SSO) version 8.0.