NXP-29529: Allow to update nuxeo Helm chart dependencies (elastic) #91
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When adding the elastic Helm chart repository, https://helm.elastic.co/, running `helm dependency update nuxeo` fails with `Killed` and exit code 137. This is most certainly due to an OOM error, maybe because the elastic Helm chart repository has a lot of content. Increasing the pod memory limit fixes the issue.
|
View issue in JIRA: NXP-29529: Upgrade to Elasticsearch 7.9.1 |
kevinleturc
approved these changes
Sep 16, 2020
bdelbosc
approved these changes
Sep 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When adding the elastic Helm chart repository, https://helm.elastic.co/, running
helm dependency update nuxeofails withKilledand exit code 137.This is most certainly due to an OOM error, maybe because the elastic Helm chart repository has a lot of content.
Increasing the pod memory limit fixes the issue.