test: enhance e2e debuggability by capturing resource changes and storing them as artifacts

[dpadhiar]

Fixes #276

Modifications

To add to the controller artifacts that we currently have, it is also useful to track information of all the resources and their child resources. The best way to do this would be to store the output of kubectl get <resource> -o yaml anytime there is a change. We can achieve this by using a watch.Interface to watch each resource and generate an output file <resource>.yaml that continually receives the updated resource YAML every time a change occurs.

Verification

Ran make test-e2e locally to verify resource file are output correctly.

Verified artifacts are uploaded when test fails on Github CI.

Failed commit: 218e6b4

[juliev0]

Looks like we watch the entire resource Kind for each file generated. That seems fine. In the future, perhaps we will generate multiple files per resource name. But right now we don't have that need, since for these resources at least we only have one of each.

[dpadhiar]

Looks like we watch the entire resource Kind for each file generated. That seems fine. In the future, perhaps we will generate multiple files per resource name. But right now we don't have that need, since for these resources at least we only have one of each.

Sounds good, this would be a pretty simple change when we need it: just adding the resource name as a parameter and using it in the label selector.