Skip to content

fix(local): cap keycloak jvm heap and raise nats helm wait timeout #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
drobertson123 wants to merge 1 commit into
base: main
Choose a base branch
from
+21 −2
Open

fix(local): cap keycloak jvm heap and raise nats helm wait timeout #79

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions local/infra/keycloak/keycloak.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,10 +18,10 @@ spec:
resources:
requests:
cpu: "100m"
memory: "550Mi"
memory: "1Gi"
limits:
cpu: "1000m"
memory: "550Mi"
memory: "1536Mi"
Comment on lines 18 to +24

@FrankSpitulski FrankSpitulski Jun 15, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@drobertson123 I tuned the usage pretty low on purpose, so it can fit on smaller machines. It should be using ~80-90% of the requested memory. I measured a run just now at 458MiB used. The e2e tests in CI show the deployment success. Are you running additional activity on keycloak outside of the normal test flow?

unsupported:
podTemplate:
spec:
Expand All @@ -35,6 +35,13 @@ spec:
- "--verbose"
- "start"
- "--import-realm"
env:
# Constrain the JVM heap so heap + non-heap RSS fits inside the
# container memory limit. Without this, Quarkus defaults to
# MaxRAMPercentage=70%, and heap + metaspace/GC/buffers exceed the
# limit and the pod is OOMKilled during the build phase.
- name: JAVA_OPTS_KC_HEAP
value: "-Xms256m -Xmx768m"
Comment on lines +39 to +44
volumeMounts:
- name: realm-import
mountPath: /opt/keycloak/data/import
12 changes: 12 additions & 0 deletions local/nats/skaffold.releases.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,10 @@ deploy:
tolerateFailuresUntilDeadline: true
helm:
flags:
# Helm's default --wait timeout is 5m; the mTLS NATS cluster can take
# longer to become ready on slower/loaded machines, so give it headroom.
upgrade:
- --timeout=15m
Comment thread
FrankSpitulski marked this conversation as resolved.
depBuild:
- --repository-config=local/helm/repositories.yaml
releases:
Expand Down Expand Up @@ -61,6 +65,10 @@ deploy:
tolerateFailuresUntilDeadline: true
helm:
flags:
# Helm's default --wait timeout is 5m; the mTLS NATS cluster can take
# longer to become ready on slower/loaded machines, so give it headroom.
upgrade:
- --timeout=15m
depBuild:
- --repository-config=local/helm/repositories.yaml
releases:
Expand Down Expand Up @@ -91,6 +99,10 @@ deploy:
tolerateFailuresUntilDeadline: true
helm:
flags:
# Helm's default --wait timeout is 5m; the mTLS NATS cluster can take
# longer to become ready on slower/loaded machines, so give it headroom.
upgrade:
- --timeout=15m
depBuild:
- --repository-config=local/helm/repositories.yaml
releases:
Expand Down