-
Spike
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
False
-
None
-
False
-
No
-
-
WHY
There a number of tests that use tooling in production pods to preform tests against other pods in the production. This a bad practice and adds dependences on the production images which could be removed at any time.
WHAT
There are a number of test that use execToPod. These test should be reviewed to and a plan form removing the need to exec commands from production pods removed.
When looking at the solution to removing these dependence on production pods the test will need to work when not running on cluster. There are external teams that also use the test suite and they may not be the tests from the cluster.
HOW
- to deploy the test container to a cluster with Delorean follow this guide
- Run the test container locally with following
ORG=yourquayorg make image/external/build ORG=yourquayorg make image/external/push docker run -it -e OPENSHIFT_HOST='https://api.yourcluster-955-2356.sr42.s1.devshift.org:6443' -e OPENSHIFT_PASSWORD='yourpassword' -e MULTIAZ=false -e DESTRUCTIVE=false -e NUMBER_OF_TENANTS='2' -e TENANTS_CREATION_TIMEOUT='3' -e RegExpFilter='C01' -e OUTPUT_DIR=c01-test-run-result -v "$(pwd)/c01-test-run-result:/c01-test-run-result:Z" quay.io/yourquayorg/integreatly-operator-test-external:latest
DONE
- list of affected test and the approach to resolved the dependence issue