Skip to content

Keep hand-raised memory limits across oap install - #52

Open
josephschorr wants to merge 1 commit into
mainfrom
install-preserve-memory-limit
Open

josephschorr wants to merge 1 commit into
mainfrom
install-preserve-memory-limit

Conversation

@josephschorr

Copy link
Copy Markdown
Member

Re-running oap install no longer resets a component's memory limit to the bundled default. If an operator has raised a limit on the cluster (for example, to stop the operator from being OOM-killed on a busy install), install keeps that value and says so in its output. Fresh installs are unchanged.

oap install used to reset every component's memory limit to the bundled
value, so a limit raised by hand to stop an OOM crashloop was undone by
the next upgrade. Install now reads the live Deployment/StatefulSet and
carries its container memory limits forward.
@vercel

vercel Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
openagentprimitives Ignored Ignored Preview Nov 5, 2026 7:24pm UTC

Request Review

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant