IBM Maximo: Provide you customization binaries.zip on OpenShift

From Wiki
Revision as of 12:31, 3 July 2025 by Ebasso (talk | contribs) (Created page with "Uploading customization_binaries.zip directly to OpenShift simplifies deployment by avoiding external image builds and registries. It enables faster updates and avoid problem with security teams. = Procedure = Start by creating a new project: oc new-project nginx-custom-binaries Create a New App Using the NGINX Template oc new-app --template=openshift/nginx-example --name=nginx-custom Check the Pod Name oc get pods Look for the pod name that starts with ngi...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Uploading customization_binaries.zip directly to OpenShift simplifies deployment by avoiding external image builds and registries. It enables faster updates and avoid problem with security teams.

Procedure

Start by creating a new project:

oc new-project nginx-custom-binaries

Create a New App Using the NGINX Template

oc new-app --template=openshift/nginx-example --name=nginx-custom 

Check the Pod Name

oc get pods

Look for the pod name that starts with nginx-custom-. You’ll need this for the next step.

Upload custominization_binaries.zip

oc cp customization_binaries.zip <pod-name>:/usr/share/nginx/html/customization_binaries.zip

Check the Route to Access Your App

oc get routes

This will show the external URL where your custom NGINX content is being served.

http://xxxxxx/custominization_binaries.zip


Ver também