Increase Keycloak container memory limit by 500MB

[sberyozkin]

Fixes #47102.

The current Keycloak container memory limit was designed to support running it in constrained environments, but unfortunately it causes side-effects, with no obvious logic.

For example, on my laptop I've never heard any issues with the 750 MB limit.
On my new laptop, which has twice as much memory and disk storage compared to the old laptop, it fails.

Users who have reported the side-effect before, confirmed 1.2 GB is sufficient for a case with the custom realm, and it works on my laptop.

I propose to increase it now and for Keycloak experts, @mabartos, and others, to investigate further.
I'm not sure about setting JAVA_OPTS_KC_HEAP="-XX:MaxRAMPercentage=50 -XX:MinRAMPercentage=50" by default without further analysis

[michalvavrik]

Yeah, I have also experienced OOM when running unit tests in OIDC extension. +1 but 1250M is a lot, let's hope someone finds a time and investigate this.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit cc81959.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[github-actions]

🎊 PR Preview 75b67ec has been successfully built and deployed to https://quarkus-pr-main-47340-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit cc81959.

Failing Jobs

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✔️	JVM Integration Tests - JDK 17			Logs	Raw logs	🔍
✖	JVM Integration Tests - JDK 17 Windows	Build	Failures	Logs	Raw logs	🔍
✔️	JVM Integration Tests - JDK 21			Logs	Raw logs	🔍

You can consult the Develocity build scans.

Failures

⚙️ JVM Integration Tests - JDK 17 Windows #

- Failing: integration-tests/oidc-wiremock-logout 

📦 integration-tests/oidc-wiremock-logout

✖ Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.5.2:test (default-test) on project quarkus-integration-test-oidc-wiremock-logout:

See D:\a\quarkus\quarkus\integration-tests\oidc-wiremock-logout\target\surefire-reports for the individual test results.
See dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
There was an error in the forked process

[mabartos]

@sberyozkin I'm ok to increase the limit for now, and I'll check it further. Thanks!

[sberyozkin]

Thanks, one of the integration tests fails on Windows during the docker environment checks, I'll tune it separately