Chapter 5. Deploying Quarkus applications as an OpenShift Serverless service
You can deploy your Quarkus applications to OpenShift Serverless using the Docker build strategy. By using OpenShift Serverless Knative Serving, you can scale services up and down depending on the load size. Scaling down services that are currently not requested improves memory capabilities.
Your Quarkus project includes pre-generated Dockerfiles with instructions. When you want to use a custom Dockerfile, you need to add the file in the src/main/docker
directory or anywhere inside the module. Additionally, you need to set the path to your Dockerfile using the quarkus.openshift.jvm-dockerfile
property for JVM mode and quarkus.openshift.native-dockerfile
property for native mode.
The following procedure demonstrates how to deploy a Serverless Quarkus Java application or a Serverless application compiled to a native executable using the Quarkus OpenShift extension.
Prerequisites
-
Have a Quarkus Maven project that includes the
quarkus-openshift
extension. Login to OpenShift using
oc
and select your project.- To verify the OpenShift project namespace, see Verifying the OpenShift project namespace.
- OpenShift Serverless operator is installed.
- OpenShift Knative Serving is installed and verified. See Installing Knative Serving.
- For native compilation, a Linux X86_64 operating system or an OCI (Open Container Initiative) compatible container runtime, such as Podman or Docker is required.
Procedure
- Change to the directory that contains your Quarkus project.
Configure the following properties in your
application.properties
file:Set Knative as a deployment target:
quarkus.kubernetes.deployment-target=knative
Set the Docker build strategy:
quarkus.openshift.build-strategy=docker
Direct OpenShift Serverless to pull your container image from the OpenShift internal registry:
quarkus.container-image.registry=image-registry.openshift-image-registry.svc:5000
NoteIf your OpenShift
<project_name>
is different from theusername
of the host system, set the group for the container image otherwise Quarkus cannot pull the image from the image registry.quarkus.container-image.group=<project_name>
(Optional) If you are using an untrusted certificate, configure the
KubernetesClient
:quarkus.kubernetes-client.trust-certs=true
(Optional) Expose the service to create an OpenShift route:
quarkus.openshift.expose=true
(Optional) Set the path to your custom Dockerfile:
quarkus.openshift.jvm-dockerfile=<path_to_your_dockerfile>
The following example shows the path to the
Dockerfile.custom-jvm
:quarkus.openshift.jvm-dockerfile=src/main/resources/Dockerfile.custom-jvm
(Optional) To deploy a Serverless application compiled to a native executable, you need to configure the following properties:
Set the container runtime:
quarkus.native.container-build=true
Specify the container engine:
To build a native executable with Podman:
quarkus.native.container-runtime=podman
To build a native executable with Docker:
quarkus.native.container-runtime=docker
(Optional) Set the path to your custom Dockerfile:
quarkus.openshift.native-dockerfile=<path_to_your_dockerfile>
Package and deploy your Serverless application to OpenShift using one of the following options:
Deploy a Quarkus Java application:
./mvnw clean package -Dquarkus.kubernetes.deploy=true
Deploy a Quarkus native application:
./mvnw clean package -Pnative -Dquarkus.kubernetes.deploy=true
Verification
View a list of pods associated with your current OpenShift project:
oc get pods
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>