Chapter 6. Using S2I to deploy Quarkus applications to OpenShift

Procedure

1. Change to the directory that contains your Quarkus Maven project.
2. Create a hidden directory called .s2i at the same level as the pom.xml file.

3. Create a file called environment in the .s2i directory and add the following content:

   ARTIFACT_COPY_ARGS=-p -r lib/ *-runner.jar

4. Commit and push your changes to the remote Git repository.

5. To import the supported OpenShift image, enter the following command:

   oc import-image --confirm ubi8/openjdk-11 --from=registry.access.redhat.com/ubi8/openjdk-11

   Note

   If you are deploying on IBM Z infrastructure, enter oc import-image --confirm openj9/openj9-11-rhel8 --from=registry.redhat.io/openj9/openj9-11-rhel8.

   For information about this image, see the Red Hat OpenJ9 11 Java Applications on RHEL8 page.

6. To build the project in OpenShift, enter the following command where <git_path> is the path to the Git repository that hosts your Quarkus project and <project_name> is the OpenShift project that you created.

   oc new-app ubi8/openjdk-11 <git_path> --name=<project_name>

   Note

   If you are deploying on IBM Z infrastructure, enter oc new-app openj9/openj9-11-rhel8 <git_path> --name=<project_name>.

   This command builds the project, creates the application, and deploys the OpenShift service.

7. To deploy an updated version of the project, push any updates to the Git repository then enter the following command:

   oc start-build <project_name>

Verification

1. View a list of pods associated with your current OpenShift project:

   oc get pods

2. To retrieve the log output for your application’s pod, enter the following command where <pod_name> is the name of the latest pod prefixed with the name of your application:

   oc logs -f <pod_name>