liveBook · Manning

OpenShift deployment manifest

As explained in Quarkus in Action

An OpenShift deployment manifest is a YAML or JSON resource definition file containing the OpenShift objects required to deploy an application.

An OpenShift deployment manifest is a generated YAML or JSON resource definition that assembles the objects needed to deploy an application. Quarkus produces openshift.yml and openshift.json alongside Kubernetes manifests when the OpenShift extension is enabled. section 11.3.4

Apply the generated manifest

Configure the OpenShift builder and route exposure, then apply the generated file with oc apply -f inventory-service/target/kubernetes/openshift.yml. Inspect pods and routes with oc get pods and oc get routes.

How Quarkus in Action covers it

How deep it goes
Explains the manifest’s Service, ImageStream, BuildConfig, and Deployment resources, then demonstrates application and verification commands.
Examples
Uses the Inventory service, generated openshift.yml, JDK and application ImageStreams, S2I builds, routes, and oc inspection commands.
What it assumes
Assumes a Quarkus application and OpenShift access, while demonstrating the required OpenShift extension and generated resource structure.
What you can do after
Operate/configure an OpenShift deployment by generating, applying, exposing, and inspecting a Quarkus manifest.
How it connects
Connects Kubernetes manifests with OpenShift resources, ImageStreams, BuildConfig, S2I, container images, Services, and Deployments.
Cover of Quarkus in Action
liveBookmanning.com
Read Quarkus in Action on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Quarkus in Action. The section links point to the parts of the book it draws on.