Quarkus - Deploying on Kubernetes and OpenShift

• The deployment of the application to OpenShift

This guide takes as input the application developed in the native application guide.So, you should have been able to package your application as a binary executable, copied it in a Docker image and run this image.

Depending on whether you are a bare Kubernetes user or an OpenShift user, pick the section you need.The OpenShift section leverages OpenShift builds and routes features which are not available in bare Kubernetes.

For this guide you need:

• being able to package the docker image from the

We recommend to follow the instructions in the next sections and build the application step by step.However, you can go right to the completed example.

Clone the Git repository: , or download an archive.

The solution is located in the directory.

Once the image has been pushed to the Kubernetes image registry, instantiate the application as follows:

The application is now exposed as an internal service. If you are using , you can access it using:

In this section, we are going to leverage the build mechanism of OpenShift. Run:

Your application is accessible at the printed URL.

This guide covered the deployment of a Quarkus application on Kubernetes and OpenShift.However, there is much more, and the integration with these environments has been tailored to make Quarkus applications execution very smooth.For instance, the health extension can be used for health check; the configuration support allows mounting the application configuration using config map, the metric extension produces data scrappable by Prometheus and so on.