Bump memory requests according to values seen in testing

[jean-edouard]

What this PR does / why we need it:
This PR bumps up the memory requests for various components (namely virt-operator, virt-api and virt-handler).
I took the highest values seen in recent testing and rounded them up. These are the values:
virt-operator: 380MB
virt-api: 300MB
virt-controller: 250MB
virt-handler: 270MB

Having values that are too low not only triggers many KubeVirtComponentExceedsRequestedMemory alerts, but also risks getting killed on busy nodes.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:
These values are high, but they just represent our current consumption.
As a separate effort, we need to investigate the high memory needs of our components, and hopefully find ways to lower them.
virt-operator is especially concerning.

Release note:

NONE

[jean-edouard]

/cherry-pick release-0.53

[kubevirt-bot]

@jean-edouard: once the present PR merges, I will cherry-pick it on top of release-0.53 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.53

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.

[rmohr]

One source for big memory consumption with many informers could be managedFields: kubernetes/kubernetes#107507

[enp0s3]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enp0s3

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 [enp0s3]

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

[Barakmor1]

/lgtm

[brianmcarey]

/retest-required

[dhiller]

/retest-required

[acardace]

/retest-required

[kubevirt-bot]

@jean-edouard: new pull request created: #8687

In response to this:

/cherry-pick release-0.53

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.

[jean-edouard]

/cherry-pick release-0.49

[kubevirt-bot]

@jean-edouard: #8613 failed to apply on top of branch "release-0.49":

Applying: Bump memory requests according to value seen in testing
Using index info to reconstruct a base tree...
M	manifests/generated/operator-csv.yaml.in
M	pkg/virt-operator/resource/generate/components/daemonsets.go
M	pkg/virt-operator/resource/generate/components/deployments.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/virt-operator/resource/generate/components/deployments.go
CONFLICT (content): Merge conflict in pkg/virt-operator/resource/generate/components/deployments.go
Auto-merging pkg/virt-operator/resource/generate/components/daemonsets.go
Auto-merging manifests/generated/operator-csv.yaml.in
CONFLICT (content): Merge conflict in manifests/generated/operator-csv.yaml.in
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bump memory requests according to value seen in testing
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-0.49

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.

[acardace]

/cherry-pick release-0.58

[kubevirt-bot]

@acardace: new pull request created: #8709

In response to this:

/cherry-pick release-0.58

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.