registry memory resource limit test is flaking

[bparees]

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/203/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/1079/

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/203/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/1073/

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/203/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/1057/

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/203/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/1049/

configuration_test.go:69: expected memory limit of 512Mi, found: 0

Given that the test creates the registry resource w/ the memory limit set, i can't see why we'd ever create a pod that didn't have the limit set, but it's the most consistent flake i'm seeing on the registry operator repo right now.

/cc @coreydaley @legionus @dmage

[bparees]

on top of that we default the deployment pod spec template resources to 256Mi, so it should literally never be zero. Perhaps something weird going on at an admission level w/ the api server, @openshift/sig-master ?

[bparees]

well i take that back. we set a request value by default and that shows up, but the limit value we set in the test is what intermittently does not show up. Perhaps we are sometimes finding the old pod.