Skip to content
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

Jump to bottom

Increase Kuma sidecar memory limit #83

Open
lobkovilya opened this issue Sep 5, 2023 · 5 comments
Open

Increase Kuma sidecar memory limit #83

lobkovilya opened this issue Sep 5, 2023 · 5 comments
Labels
triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@lobkovilya
Copy link
Contributor

The default memory limit is 512Mi and sometimes could be exceeded. This results in test failure like https://github.com/Kong/mesh-perf/actions/runs/6078636182/job/16490081440.
@github-actions github-actions bot added the triage/pending This issue will be looked at on the next triage meeting label Sep 5, 2023
@jakubdyszkiewicz
Copy link
Contributor

Triage: check if a failing sidecar does not follow too many services. Watch out for empty string in reachable service

@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Sep 5, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 5, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Dec 5, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Dec 5, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Mar 5, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Mar 5, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz removed the triage/stale Inactive for some time. It will be triaged again label Mar 6, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jun 5, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jun 5, 2024
@lobkovilya lobkovilya removed the triage/stale Inactive for some time. It will be triaged again label Jun 10, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Sep 9, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Sep 9, 2024
@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@slonka @jakubdyszkiewicz @lobkovilya @lukidzi