Correct the indentation typo with resource requests

[Rajalakshmi-Girish]

The indentation was wrong for resources metadata in jobs test-e2e-capi-ibmcloud-periodics.yaml, test-etcd-periodics.yaml and etcd-postsubmit.yaml, and hence no proper resources were allocated to the jobs.
I see the TestWatchDelay related flakiness improve to a major extent after proper resource allotment.

[mkumatag]

I'm not sure about this, will it make any difference when we just have a key without requests.. cc @Karthik-K-N

anyways this is a invalid syntax which needs a fix, hence merging.

[ppc64le-cloud-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mkumatag, Rajalakshmi-Girish

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mkumatag]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mkumatag]

/lgtm

[ppc64le-cloud-bot]

@Rajalakshmi-Girish: Updated the job-config configmap in namespace prow at cluster default using the following files:

• key test-e2e-capi-ibmcloud-periodics.yaml using file config/jobs/periodic/cluster-api-provider-ibmcloud/test-e2e-capi-ibmcloud-periodics.yaml
• key test-etcd-periodics.yaml using file config/jobs/periodic/etcd/test-etcd-periodics.yaml
• key etcd-postsubmit.yaml using file config/jobs/ppc64le-cloud/builds/etcd-postsubmit.yaml

In response to this:

The indentation was wrong for resources metadata in jobs test-e2e-capi-ibmcloud-periodics.yaml, test-etcd-periodics.yaml and etcd-postsubmit.yaml, and hence no proper resources were allocated to the jobs.
I see the TestWatchDelay related flakiness improve to a major extent after proper resource allotment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mkumatag]

@Rajalakshmi-Girish lets think about how to avoid such issues in the feature, can we add some linting to catch such issues? not sure if there is a way..

[Rajalakshmi-Girish]

I'm not sure about this, will it make any difference when we just have a key without requests.. cc @Karthik-K-N

anyways this is a invalid syntax which needs a fix, hence merging.

All these days, etcd job has been sending only resources: {} in job yaml due to this invalid syntax.

When I tested etcd flakes locally as well, most of the time the host had resource limitations.
Running the long pending TestWatchDelay flake on a pod with required resources, displayed 0 failure for 30m of stress run.
@mkumatag @srivastav-abhishek