Container Deployments - Use one common prerequisite script

Having one script, that has the same name in each upgrade, that does all the prerequisite work will help cut back on deployment problems. This is especially important with SSP container upgrades. In the FixList.txt there are two scripts to delete the security context and two scripts to add security context.

Looking at the scripts required by SSP install/upgrade, the first is run without flags and the second run using the project or namespace as the flag. The create scripts work the same. These are relatively small scripts. Would it be possible for IBM going forward to add all 4 to one script with one default name/standard name? A script that captures and prints out previous settings, new settings and verifies the project space name. Even if there are no changes that need to be run still have a default prerequisite script that uses the same name each time.

This allows companies/users to create a pipeline that calls the default prerequisite script. A pipeline will track and keep a history of script runs (if they call the same script name) and helm upgrades. The second thing it does is cut back on errors like we experienced with the scripts being executed in the wrong namespace.

If the scripts can't be combined into one default prerequisite script, it would be nice if there was some namespace verification or namespace print out added to scripts. If the scripts can run an "oc project" and have the user verify they are in the proper namespace this would super useful. Preventing errors or problems in an already complicated OpenShift environment.

As our company found out the hard way running scripts that change the security context in the wrong name space can take down applications that need specific permissions to run.

Having one script name to run each time before or after a helm upgrade would cut down on errors. With pipelines you don't have to worry about running the command in the wrong environment because they are project/namespace specific.