Intro To OpenShift
Deploying the Old-Fashioned Way

• Production promotions are a laborious, manual process

• Developers have little to no control over dev environments

-Bamboo improved some of this, but not nearly enough

• Load balancing is available but is still somewhat manual

• Application monitoring requires a watchdog program

Deploying the Old-Fashioned Way

• Production promotions are a laborious, manual process

• Developers have little to no control over dev environments

-Bamboo improved some of this, but not nearly enough

• Load balancing is available but is still somewhat manual

• Application monitoring requires a watchdog program

Why OpenShift?
• Easy setup and deployment
• Automatic load balancing
-Will spin up extra pods when it detects traffic above a certain threshold
-This is configurable – can also manually add or remove pods
• Configuration files hosted and edited within OpenShift
-Passwords can be injected using secrets
• Jenkins plugin allows for automated builds
• Pipelines can be set up to push apps to multiple projects with one click (or a commit to a specified branch)
 
OpenShift Setup
• Install cluster and configure users
• Create a project or projects
• Add an application to the project
-Build an image
-Inject properties as needed
-Create a route to allow external access to the app
• Set up a build and a pipeline
-Can use multiple of each, if different branches need automatic deployment
 
OpenShift Setup
 
Intro To OpenShift

Introductory view into deploying Java applications using Red Hat OpenShift. This presentation will provide a very basic introduction into the deployment process using Red Hat OpenShift. OpenShift enables continuous integration using pipelines. Pipelines can also be used to manually deploy applications.