Skip to content

Red Hat Single Sign-On 7.6.2 for OpenJDK on OpenShift multiarch container image

Compare
Choose a tag to compare
@iankko iankko released this 13 Mar 14:44
· 33 commits to sso76-dev since this release

The v7.6.2.GA release of Red Hat Single Sign-On multiarch container image for OpenJDK running on OpenShift.

The container image supports (can be run on top of) the following three architectures: x86_64, s390x, and / or ppc64le.

Backward-Incompatible Changes:

The logic of JBoss DMR probe implementation, used by readinessProbe.sh and livenessProbe.sh scripts (readiness / liveness probes) was modified to use so called probe netrc file instead of a plaintext username & password credentials to authenticate the probe user account, when issuing a probe request against the JBoss DMR API.

As a result of this change, when:

  • The readinessProbe.sh script of the Red Hat Single Sign-On 7.6.2 for OpenJDK on OpenShift container image is called as the readiness probe implementation (the default when a RH-SSO pod is provisioned via some of the available RH-SSO OpenShift templates), or
  • The livenessProbe.sh script of the Red Hat Single Sign-On 7.6.2 for OpenJDK on OpenShift is called as the liveness probe implementation (the default when a RH-SSO pod is provisioned via some of the available RH-SSO OpenShift templates)

the RH-SSO deploment config now requires an emptyDir, tmpfs based (emptyDir.medium field set to "Memory") persistent volume, mounted under "/mnt/rh-sso" directory to store the netrc file to be used for probes.

The available RH-SSO OpenShift templates were modified:

to automatically add this newly required /mnt/rh-sso volume for new deployments. Therefore, users of RH-SSO OpenShift templates are strongly encouraged to update to the latest v7.6.2.GA version of the templates.

If you need to:

  1. Run the RH-SSO 7.6.2.GA for OpenShift container image with some of previous versions of the RH-SSO templates,
  2. Or run the RH-SSO 7.6.2.GA for OpenShift container image without a template, but calling the readinessProbe.sh script (or livenessProbe.sh script respectively) as part of the container image run,

you need to add this newly required volume manually..

Other Notable Changes Compared To Previous Release:

  • Default implementation of the readiness probe (readinessProbe.sh script) now also checks if a connection can be established to all of the defined XA and non-XA datasources,
  • A bug, when using CONFIG_ADJUSTMENT_MODE set to cli was corrected,
  • A bug, when using JSON log format was corrected

Full Changelog: v7.6.1.GA...v7.6.2.GA