Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that OpenShift customers are using or might want to run. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for OpenShift Container Platform.
This list of tested integrations will expand over time, however this page is limited to only covering what OpenShift supported at the time the minor version GA'ed. This means that it is possible for other configurations to be "tested" and/or "supported" that are not listed. One such common example, is OCP support on RHEL minor version updates. Because RHEL and OCP have independent lifecycles, its possible for RHEL to update, to say 7.Y, but for this page to only say OCP 3.Y only is "tested/supported" with 7.Y-1. In the case of RHEL (and its updates), these types of configurations are always "tested" and "supported", however this document may not reflect this because it captures what OCP supported at the time it GA'ed.
For example, the following table below shows 7.3, 7.4 are tested version at the timing of OCP 3.6. It means that we tested these combinations at the
timing of OCP 3.6 GA. Red Hat will provide support for the combination of OCP 3.6 and RHEL 7.5 or later.
Red Hat provides both production and development support for the tested integrations in the same major version family at or above the tested version according to your subscription agreement. Earlier versions of a tested integration in the same major version family are supported on a commercially reasonable basis.
For a general list of supported OpenShift images, you can look at the This content is not included.Red Hat Container Registry for openshift3 images. These images are provided as part of the OCP platform and are meant to provide functional capabilities or resources to OCP. The images are not supported as general purpose application images.
Below is a list of supported images that are intended to be used as base layer images, and provide functionality to developers on the OpenShift platform.
Images denoted with a * above are found in the S2I and Database Images sections are released outside of OpenShift 15 and have an independent life cycle, see the SCL Lifecycle Page and .Net Lifecycle Page for more information.
Note: Images in the S2I and Database Images sections found under the openshift3 repository were deprecated with 3.5 in favor of newer versions of such images found in SCL repositories.
Note: The Middleware for Openshift section lists the product imagestream versions that have been tested with specific Openshift versions at the time of an Openshift release. Newer versions of middleware product images may be used across versions of Openshift. Specific incompatibilities may be designated in this table from time to time.
A full range of platform tests has been performed on the following tested configurations. Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each OpenShift Enterprise release. This list of tested integrations will expand over time.
Red Hat provides production support31 for the tested integration's in the same major version family at or above the tested version according to your subscription agreement. Earlier versions of a tested integration in the same major version family are supported on a commercially reasonable basis.
Technology Preview: Some Operating Systems were not fully supported with some releases, and support was only offered with Technology Preview Status. Please see https://access.redhat.com/support/offerings/techpreview for more details. 2: Due to RHEL Extras and the docker package, changes to RHEL atomic host are needed to remain in a supported configuration. See Solution 3414221 for more details. 3: Same as 2 4: With the GA of OpenShift 3.7 we improperly documented that Ansible 2.4.0* and 2.4.1* were supported with this version of OCP. While these versions were tested, they were tested to help ensure compatibility with the new Ansible release channels, and were not intended to be used to install/upgrade the product. Please see the 3.7 Release Notes for where we documented this change. 6: With OpenShift 3.2.1 we added support for Docker 1.10 7: Plug-in Component: The product version denoted is not shipped or provided by Red Hat but is detected as plug-ins shipped with the OpenShift product are tested with this third party product. 8: NFS versions that we test with are the same for NFSv3 and NFSv4, however the configuration determines what protocol version we use when testing. 9: GlusterFS comparability as it pertains to CNS/OCS can be found on article 2356261 10: Images (denoted by image name) used for installation on Atomic Host or in pure docker installs. 11: Support for these images did not start until OpenShift Container Platform (OCP) 3.1.1. In OCP 3.1, these were in a Technology Preview status. 12: Images denoted in this section apply to the openshift3, rhscs, and dotnet namespace on the registry 13: We introduced a versioning change with the 3.2 (s2i and database) images that no longer is tied to the OpenShift release. Image version are now tagged based on the component version they represent. 14: Same as 8 15: Images denoted in this section apply to the rhscl and dotnet namespace on the registry 16: xPaaS Image Support, or usage, is limited to the OpenShift platform. 17: Image version with this designation may only be supported on OCP minor point releases (3.0.2), due to incompatibility issues. 18: Same as 12. 19: Same as 13. 20: This is not meant to be used in production, but is provided for POC and Development Usecases. 21: Supported after v3 API version (3.0.2.902-0) of Keystone as provided by Red Hat OpenStack. 22: Same as 20 23: Same as 20 24: Same as 20 25: Same as 20 26: Same as 20 27: Same as 20 28: Same as 20 29: Same as 20 30: Same as 20 31: Development support can also be offered through Layered Product Entitlements. 32: Red Hat supports many Certified Cloud Providers and any cloud provider on the list is “supported” so long as it supports RHEL as a base OS (see above for versions). However, we do not explicitly test OCP on all CCPs, so the scope of support may be limited. 33: Red Hat provides support for Red Hat Enterprise Linux based on the hypervisors listed in https://access.redhat.com/certified-hypervisors as such OpenShift as a platform is supported on these hypervisors but may not be explicitly listed as a tested Infrastructure Layer. 34: Red Hat has limits on the number VMs that can be run with a subscription for KVM. Review https://access.redhat.com/articles/rhel-kvm-limits for limit restrictions. 35: Red Hat OpenStack has limits on the various components. Be sure that any OpenShift deployment on top of OpenStack fits within the defined limits by reviewing https://access.redhat.com/articles/1436373. 5: Please see our release notes on an update to the supported version of ansible