How to deploy Traffic Parrot in OpenShift

A significant number of Traffic Parrot customers run our tool in OpenShift. This blog post discusses a template process you can follow to do the same. 

Here’s a quick terminology review to get us on the same page:

• docker = used to build, push and run container images
• podman = docker replacement that OpenShift recommend using (developed by OpenShift), almost identical to standard docker
• oc = OpenShift command line interface to deploy and configure OpenShift services etc.
• helm = tool used to package and deploy OpenShift applications automatically
• TPLS = Traffic Parrot License Server
• TP = Traffic Parrot

If the end goal is to deploy Traffic Parrot in OpenShift, you need the following:

• TPLS Docker image built and pushed to OpenShift Docker registry
• TPLS Helm Chart built and deployed to OpenShift Cluster
• TP Docker image built and pushed to OpenShift Docker registry
• TP Helm Chart built and deployed to OpenShift Cluster

There will be several steps to deploy things in OpenShift that we need to go through:

1. (One-time learning) Discuss the industry standard Docker and OpenShift workflow
2. (One-time setup) Establish OpenShift cluster connectivity from your localhost
3. (One-time setup) Establish Docker registry connectivity from your localhost
4. (One-time learning) Discuss the client-specific OpenShift workflow (there may be additional steps beyond the industry standard ones)
5. (One-time setup) Create a TPLS Docker image using podman
6. (One-time test) Deploy TPLS in OpenShift using oc and test it works as expected
7. (One-time test) Test that localhost TP can connect to OpenShift TPLS
8. (One-time setup) Create a TP Docker image using podman
9. (One-time test) Deploy TP and TPLS in OpenShift using oc and test it works as expected
10. (One-time setup) Create a pipeline to deploy TPLS in OpenShift from GitHub sources
11. (One-time setup) Create a pipeline to test TP API mocks and  deploy TP in OpenShift from GitHub sources
12. (One-time setup) Create a client internal confluence page for API mocks developers on how to make changes to Traffic Parrot client API mocks and deploy them using the automated pipelines
13. (One-time test) Test TP API mocks with a selected use case
14. (Ongoing process) Develop TP API mocks locally, then commit configuration to GitHub (which will be deployed by a pipeline automatically to OpenShift)
15. (Ongoing process) Run TP pipeline to test TP API mocks and deploy to OpenShift automatically with rolling releases for partners

We can help you with all those by providing standard scripts our customers use.