Skip to content

Webinar: Three ways to deploy a Python app into an OpenShift cluster

Photo of Anchal Bhalla
Hosted By
Anchal B.
Webinar: Three ways to deploy a Python app into an OpenShift cluster

Details

This webinar will show you how to deploy a Python application into an OpenShift cluster on the cloud. You can also use the methodology described here to deploy applications or microservices developed on other runtime environments.

This webinar will cover three deployment scenarios to build and deploy applications to an OpenShift cluster on IBM Cloud:

  1. An existing Docker image needs to be pushed to the OpenShift cluster on IBM Cloud, and then deployed: In this scenario, an existing Docker image is in a private registry. The image must be deployed on the OpenShift cluster on IBM Cloud. For example, you might use this deployment scenario in a “lift and shift” approach during application modernization. There is no continuous integration or delivery mechanism that is implemented, because you don’t have access to the sources.

  2. There is a GitHub repo with sources as well as a Dockerfile that has instructions to assemble the image: This scenario is applicable when you want complete control and flexibility to assemble the image with the only the required dependencies and versions. The code is always compatible with the dependencies, because you specify them. You need to maintain the Dockerfile in this scenario, which can be a complex task at times. This scenario allows continuous integration and delivery to the OpenShift cluster, which helps keep the deployed version of the code current.

  3. There is a GitHub repo with sources: In this scenario, you rely on the OpenShift Source to Image (S2I) toolkit to create a Docker image. OpenShift S2I uses the sources and a builder image to create a new Docker image. When the oc new-app ... command is used and no Dockerfile exists in the repository, the source code language is auto-detected. The language detection rules are specified here. According to the OpenShift blog, the advantages of using S2I are speed, patchability, user efficiency, and ecosystem. This scenario also allows a continuous integration and delivery to the OpenShift cluster, which helps keep the deployed version of the code current.

We will be using Red Hat® OpenShift® on IBM Cloud™ to build the code lab

Prerequisites:

Please register and join using this link:
Webinar's Webex registration link: ibm.biz/BdqjSj

----------------------------------------------------------------------------------------------------
Want to put your tech skills to good use during this time of Quarantine? Participate in "Call for Code" Global Hackathon and get a chance to win upto $200,000 by helping us solve the most challenging problems of society right now: COVID and Climate Change.

Please visit http://callforcode.org for more details and FAQs

Check out the resources & starter kits to kick-off your solution: https://developer.ibm.com/callforcode

Photo of IBM Developer Dubai group
IBM Developer Dubai
See more events