chore: increase default memory limit for embedded openvsx registry

[svor]

Signed-off-by: Valerii Svydenko vsvydenk@redhat.com

What does this PR do?

Since in DevSpaces we use another image to run the Plugin registry and openvsx is initializing at runtime, it's not enough 2Gi to start the pod. To fix the problem i want to increase the default memory limit for embedded openvsx registry to 4Gi.

What issues does this PR fix or reference?

https://issues.redhat.com/browse/CRW-3295

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• Custom resource definition file is up to date
• OLM bundles are up to date
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[openshift-ci]

@svor: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v11-devworkspace-happy-path	9562139	link	true	/test v11-devworkspace-happy-path
ci/prow/v11-che-behind-proxy	9562139	link	true	/test v11-che-behind-proxy

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[nickboldt]

If @tolusha is +1, then I am too.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nickboldt, svor, tolusha

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

Needs approval from an approver in each of these files:

• OWNERS

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

[nickboldt]

Please backport this to the 7.54.x branch, assuming we still plan to align DS 3.3 to 7.54.x