Bump the pod memory to higher levels to work on power

[mkumatag]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change

/kind bug

/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

ppc64le architecture machines by default pagesize is 64K (vs 4K on intel), this usually end up using more memory for th workloads, so to run this testcase successfully, need to increase the pod memory limits to higher lavel.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[mkumatag]

/sig testing

[mkumatag]

/assign @vishh

[mkumatag]

/priority important-longterm

[mkumatag]

/assign @Random-Liu

[mkumatag]

/sig api-machinery

[mkumatag]

/test pull-kubernetes-e2e-kops-aws

[mkumatag]

/cc @dims

[dims]

/assign @yujuhong

@kubernetes/sig-node-pr-reviews

[fedebongio]

/remove-sig api-machinery

[yujuhong]

I think the summary API test only checks that the numbers are in the right range (with no intention to track usage regression), so bumping the number should be fine.
/cc @dashpole
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mkumatag, yujuhong

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:

• test/e2e_node/OWNERS [yujuhong]

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

[dashpole]

Agree with the above, this is mostly meant to check "Is this about what we expect the pod to use?". The lower bound is also much more important than the upper bound for checking, so it is fine to raise, especially if it is failing on valid setups.
/lgtm

[mkumatag]

Thanks a lot, guys @dashpole @yujuhong @dims.

[mkumatag]

assertion for pod spec is working fine but .Node.SystemContainers[pods].Memory: is failing because I'm running tests with parallel=8(default settings) for the node test. which is resulting in exceeding the memory limit check for the whole node.

    Timed out after 60.000s.
    Expected
        <string>: Summary
    to match fields: {
    .Node.SystemContainers[pods].Memory:
    	Expected
    	    <string>: MemoryStats
    	to match fields: {
    	.UsageBytes:
    		Expected
    		    <uint64>: 430702592
    		to be <=
    		    <int64>: 400000000
    	.WorkingSetBytes:
    		Expected
    		    <uint64>: 420806656
    		to be <=
    		    <int64>: 400000000
    	}

    }

code located at: https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/summary_test.go#L116:L118

IMO we should change the limit to memoryLimit := memoryCapacity.Value() what do you say? @dashpole @yujuhong

[dashpole]

@mkumatag That sounds fine to me.

[mkumatag]

@mkumatag That sounds fine to me.

I have submitted another PR to fix this - #73196