Skip to content

ECK - Increase default Kibana memory limit to 2Gi #6770

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

Merged
eedugon merged 4 commits into from
Jun 1, 2026
Merged

ECK - Increase default Kibana memory limit to 2Gi #6770

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4477940
ECK - Increase default Kibana memory limit to 2Gi
eedugon May 29, 2026
4707c10
Update deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md
eedugon May 29, 2026
3eebd7d
suggestions implemented
eedugon Jun 1, 2026
3e00c74
Merge branch 'main' into eedugon-patch-5
eedugon Jun 1, 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
4 changes: 2 additions & 2 deletions deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -321,7 +321,7 @@ If `resources` is not defined in the specification of an object, then the operat
| --- | --- | --- |
| APM Server | `512Mi` | `512Mi` |
| {{es}} | `2Gi` | `2Gi` |
| {{kib}} | `1Gi` | `1Gi` |
| {{kib}} | `1Gi` | `2Gi` |
Comment thread
eedugon marked this conversation as resolved.
Outdated
| Beat | `300Mi` | `300Mi` |
| Elastic Agent | `400Mi` | `400Mi` |
| Elastic Maps Server | `200Mi` | `200Mi` |
Expand All @@ -330,7 +330,7 @@ If `resources` is not defined in the specification of an object, then the operat
| AutoOps Agent | `400Mi` | `400Mi` |

::::{note}
The default 1 Gi {{kib}} limit is sufficient for core functionality. For Platinum and Enterprise users, we recommend at least 2 Gi of memory for each {{kib}} instance. With less than 2 Gi, you can face service interruptions when using features such as Security detection rules, reporting, workflows, and Agent Builder.
The default 2 Gi {{kib}} limit is sufficient for core functionality. For Platinum and Enterprise users, we recommend at least 2 Gi of memory for each {{kib}} instance. With less than 2 Gi, you can face service interruptions when using features such as Security detection rules, reporting, workflows, and Agent Builder.
Copy link
Copy Markdown
Contributor

@TimBosman TimBosman May 29, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

This sounds a bit weird for me.

The default is 2 Gi, but for specific use cases we recommend 2 Gi.

We should either increase the recommendation, or remove this line from the documentation

Copy link
Copy Markdown
Contributor Author

@eedugon eedugon May 29, 2026

Choose a reason for hiding this comment

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

Yes, I agree. Even with the at least it doesn't sound nice.
Thanks for the comment

Copy link
Copy Markdown
Member

@shainaraskas shainaraskas May 29, 2026

Choose a reason for hiding this comment

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

@eedugon I added this during the window where the default compute resources were lower.

I think what this actually needs is version-awareness - I assume in older ECK versions, regardless of stack version, the default would be lower? so the default in the table would need two bullets, one for the two states, and then this note would need to be contextualized to older versions.

::::

If the Kubernetes cluster is configured with [LimitRanges](https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/) that enforce a minimum memory constraint, they could interfere with the operator defaults and cause object creation to fail.
Expand Down
Loading