Upgraded from OpenShift 4.9 to 4.10

[eric-nadeau]

Change Overview

1. Bumped up various instances of 4.9/4_9/4-9 to 4.10/4_10/4-10
   1. In these files:
      1. Makefile
      2. build/integration-test.sh
      3. pkg/app/utils.go
      4. pkg/testing/integration_register.go
   2. Based on these PRs to upgrade from 4.7 to 4.9:
      1. https://github.com/kanisterio/kanister/pull/1181/files
      2. https://github.com/kanisterio/kanister/pull/1191/files
   3. One exception was PostgreSQL's namespace
      1. Changed from postgresdepconf4-5-test to postgresdepconf4-10-test
      2. Seems we missed it in previous upgrades

Pull request type

Please check the type of change your PR introduces:

• 🚧 Work in Progress
• 🌈 Refactoring (no functional changes, no api changes)
• 🐹 Trivial/Minor
• 🐛 Bugfix
• 🌻 Feature
• 🗺️ Documentation
• 🤖 Test

Issues

• Upgrade OpenShift 4.9 support to 4.10 #1474

Test Plan

• 💪 Manual
• ⚡ Unit test
• 💚 E2E

1. Disabled minio check

   1. Ensured there were no local changes

      veeam:~/src/kanister$ git status
      On branch 1474_SupportOpenShift4.10
      Your branch is up to date with 'origin/1474_SupportOpenShift4.10'.
      
      nothing to commit, working tree clean

   2. Patched integration-test.sh

      veeam:~/src/kanister$ sed -i '' -e '/check_dependencies$/d' build/integration-test.sh

   3. Inspected the changes
      
      veeam:~/src/kanister$ git diff
      diff --git a/build/integration-test.sh b/build/integration-test.sh
      index e717318d..10827f81 100755
      --- a/build/integration-test.sh
      +++ b/build/integration-test.sh
      @@ -100,7 +100,6 @@ case "${1}" in
	       ;;
       esac

      -check_dependencies
       echo "Running integration tests:"
       pushd ${INTEGRATION_TEST_DIR}
       go test -v ${TEST_OPTIONS} -check.f "${TEST_APPS}" -installsuffix "static" . -check.v

2. Ran openshift-test
   
   1. Deployed an OpenShift 4.10 cluster
   2. Pointed ~/.kube/config to it
   3. Verified the cluster is running 4.10

      veeam:~/src/kanister$ oc version | grep Server
      Server Version: 4.10.17

   4. Ensured my environment variables were set

      veeam:~/src/kanister$ printenv | awk -F= '/AWS/{print$1}'
      AWS_ACCESS_KEY_ID
      AWS_SECRET_ACCESS_KEY
      AWS_REGION

   5. Ran openshift tests

      veeam:~/src/kanister$ /usr/bin/time -p make openshift-test
      Running integration tests:
      ~/src/kanister/pkg/testing ~/src/kanister
      === RUN   Test

      ****************************************
      *** truncated 114 lines of JSON logs ***
      ****************************************

      OK: 2 passed
      --- PASS: Test (109.93s)
      PASS
      ok  	github.com/kanisterio/kanister/pkg/testing	110.509s
      ~/src/kanister
      real 115.21
      user 6.37
      sys 4.25
      veeam:~/src/kanister$ echo $?
      0

3. Ran integration-test

   1. Deployed a plain cluster in AWS' EKS

   2. Pointed ~/.kube/config to it
      
   3. Ensured my environment variables were set

      veeam:~/src/kanister$ printenv | awk -F= '/AWS/{print$1}'
      AWS_ACCESS_KEY_ID
      AWS_SECRET_ACCESS_KEY
      AWS_REGION

   4. Called the make target to run integration tests

      veeam:~/src/kanister$ /usr/bin/time -p make integration-test DOCKER_BUILD=false
      Running integration tests:
      ~/src/kanister/pkg/testing ~/src/kanister
      === RUN   Test

      ****************************************
      *** truncated 355 lines of JSON logs ***
      ****************************************

      OK: 6 passed
      --- PASS: Test (231.88s)
      PASS
      ok  	github.com/kanisterio/kanister/pkg/testing	232.463s
      ~/src/kanister
      real 236.56
      user 18.67
      sys 7.75
      veeam:~/src/kanister$ echo $?
      0

[github-actions]

Thanks for submitting this pull request 🎉. The team will review it soon and get back to you.

If you haven't already, please take a moment to review our project contributing guideline and Code of Conduct document.

[pavannd1]

LGTM

Was thinking about removing older versions. We can address that later 👍🏼

[pavannd1]

Same as above

[pavannd1]

Should we just remove older versions? I'm confident that we don't support 3.11 anymore but we can reduce the tests to just the latest version

[eric-nadeau]

From the way the code is written it looked like we wanted to support some specific legacy versions in addition to the latest. This ticket was opened to track this idea: #1512