Skip to content

Add workarounds for Helm chart v1.1.3 installation issues #115

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

Draft
drewdrewthis wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Add workarounds for Helm chart v1.1.3 installation issues #115

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
452079f
Add workarounds for Helm chart v1.1.3 installation issues
drewdrewthis Jan 28, 2026
08237b6
docs: increase memory limits for dev mode, add OOM troubleshooting
drewdrewthis Jan 28, 2026
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
75 changes: 71 additions & 4 deletions self-hosting/kubernetes-helm.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,14 +74,21 @@ langevals:

postgresql:
chartManaged: true
image:
registry: docker.io
repository: bitnamilegacy/postgresql
tag: "16"
auth:
password: "rtfyg6j8iu"
volumePermissions:
enabled: false

redis:
chartManaged: true

opensearch:
chartManaged: true
singleNode: true
clusterName: "langwatch-test-opensearch"
```

Expand Down Expand Up @@ -206,13 +213,14 @@ app:
enabled: false
sentry:
enabled: false
# Development mode requires more memory for Turbopack compilation
resources:
requests:
cpu: 250m
memory: 512Mi
cpu: 500m
memory: 2Gi
limits:
cpu: 1000m
memory: 1Gi
cpu: 2000m
memory: 4Gi

langwatch_nlp:
resources:
Expand All @@ -234,10 +242,16 @@ langevals:

postgresql:
chartManaged: true
image:
registry: docker.io
repository: bitnamilegacy/postgresql
tag: "16"
auth:
username: postgres
password: dev-postgres-password
database: langwatch
volumePermissions:
enabled: false
primary:
persistence:
enabled: false
Expand All @@ -253,6 +267,7 @@ redis:
opensearch:
chartManaged: true
replicas: 1
singleNode: true
persistence:
enabled: false

Expand Down Expand Up @@ -426,4 +441,56 @@ metadata:

Alternatively, configure an Istio `ServiceEntry`/egress policy for your OpenSearch endpoint.
</Accordion>

<Accordion title="OpenSearch: duplicate env var error (cluster.initial_master_nodes)">
If you see an error like:

```
Error: INSTALLATION FAILED: failed to create typed patch object ... duplicate entries for key [name="cluster.initial_master_nodes"]
```

Add `singleNode: true` to your opensearch configuration:

```yaml
opensearch:
chartManaged: true
singleNode: true
```

See [issue #1232](https://github.com/langwatch/langwatch/issues/1232) for details.
</Accordion>

<Accordion title="PostgreSQL: image pull errors (bitnami/postgresql or bitnami/os-shell not found)">
If PostgreSQL pods fail with `ImagePullBackOff` or `ErrImagePull` for images like `bitnami/postgresql:16.x.x-debian-...` or `bitnami/os-shell:...`, the Bitnami images may have been removed from Docker Hub.

Use the legacy Bitnami image and disable the volumePermissions init container:

```yaml
postgresql:
chartManaged: true
image:
registry: docker.io
repository: bitnamilegacy/postgresql
tag: "16"
volumePermissions:
enabled: false
```

See [issue #1232](https://github.com/langwatch/langwatch/issues/1232) for details.
</Accordion>

<Accordion title="App crashes with exit code 137 (OOMKilled) in development mode">
Development mode uses Turbopack for on-demand compilation which requires more memory than production mode. If the app crashes with exit code 137, increase the memory limits:

```yaml
app:
resources:
requests:
memory: 2Gi
limits:
memory: 4Gi
```

For production deployments, the default 1Gi limit is usually sufficient.
</Accordion>
</AccordionGroup>
Loading