This is a cache of https://docs.openshift.com/aro/3/dev_guide/migrating_applications/support_guide.html. It is a snapshot of the page at 2024-11-23T21:01:50.461+0000.
Support Guide - Migrating Applications | Developer Guide | Azure Red Hat OpenShift 3
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
×

Support Guide

Important

Azure Red Hat OpenShift 3.11 will be retired 30 June 2022. Support for creation of new Azure Red Hat OpenShift 3.11 clusters continues through 30 November 2020. Following retirement, remaining Azure Red Hat OpenShift 3.11 clusters will be shut down to prevent security vulnerabilities.

Follow this guide to create an Azure Red Hat OpenShift 4 cluster. If you have specific questions, please contact us

Overview

This topic reviews supported languages, frameworks, databases, and markers for OpenShift version 2 (v2) and OpenShift version 3 (v3).

See Azure Red Hat OpenShift tested integrations for more information about common combinations that Azure Red Hat OpenShift customers are using.

Supported Databases

See the Supported Databases section of the Database Applications topic.

Supported Languages

Supported Frameworks

Table 1. Supported Frameworks
v2 v3

Jenkins Server

jenkins-persistent

Drupal 7

Ghost 0.7.5

WordPress 4

Ceylon

Go

MEAN

Supported Markers

Table 2. Python
v2 v3

pip_install

If your repository contains requirements.txt, then pip is invoked by default. Otherwise, pip is not used.
Table 3. Ruby
v2 v3

disable_asset_compilation

This can be done by setting DISABLE_ASSET_COMPILATION environment variable to true on the buildconfig strategy definition.
Table 4. Perl
v2 v3

enable_cpan_tests

This can be done by setting ENABLE_CPAN_TEST environment variable to true on the build configuration.
Table 5. PHP
v2 v3

use_composer

composer is always used if the source repository includes a composer.json in the root directory.
Table 6. Node.js
v2 v3

NODEJS_VERSION

N/A

use_npm

npm is always used to start the application, unless DEV_MODE is set to true, in which case nodemon is used instead.
Table 7. JBoss EAP, JBoss WS, WildFly
v2 v3

enable_debugging

This option is controlled via the ENABLE_JPDA environment variable set on the deployment configuration by setting it to any non-empty value.

skip_maven_build

If pom.xml is present, maven will be run.

java7

N/A

java8

JavaEE is using JDK8.
Table 8. Jenkins
v2 v3

enable_debugging

N/A
Table 9. All
v2 v3

force_clean_build

There is a similar concept in v3, as noCache field in buildconfig forces the container build to rerun each layer. In the s2i build, the incremental flag is false by default, which indicates a clean build.

hot_deploy

Ruby, Python, Perl, PHP, Node.js

enable_public_server_status

N/A

disable_auto_scaling

Autoscaling is off by default and it can be turn on via pod auto-scaling.

Supported Environment Variables