Add pod scenarios for custom app

[juliemathew]

Signed-off-by: mjulie mjulie@in.ibm.com

[chaitanyaenr]

@juliemathew we can definitely have the scenario part of the scenarios to consume in the config but we might want to delete the entry in the default config since the acme-air namespace might not exist on a default cluster. Thoughts?

[juliemathew]

@chaitanyaenr
I agree to your suggestion. Removed the entry in the config file and modified the ReadMe for 'Pod Scenarios'.
Please review. Thanks.

[rht-perf-ci]

Can one of the admins verify this patch?

[paigerube14]

One small suggestion, you are kind of doing a double post action check. I would suggest picking just one.

The 2 different types can be seen in the first pod_scenario section here

• the etcd scenario doesn't have a second item in the list and does the post action check in the yaml scenario file.

• While the regex scenario has a python file in the list for that scenario. The regex scenario has varying number of pods so we use the python file to print the number of pods for that specific env. If you want to use a python file or bash script as the post action check, it will first run the script before the scenario to get the original number of pods before the pod killing and again after to make sure those numbers match.
  Also, if you have a varying number of pods you can print just the number of pods as seen here and kraken will take care of the rest.

Please let me know if any of that doesn't make sense.

[chaitanyaenr]

@juliemathew we can skip the "scenarios/post_action_customapp_pod.py" action in favor of this check I guess. Thoughts?

[juliemathew]

Yes. I agree.
Made the changes. Please review. Thanks.

[chaitanyaenr]

LGTM, thanks @juliemathew.

[paigerube14]

LGTM