-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
OSC 1.9.0, OSC 1.10.0
-
None
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
-
-
Bugs and Vulnerability Issues
-
0
Description
The controller-manager OOMs with the default memory limit (256Mi)
Steps to reproduce
<What actions did you take to hit the bug?>
1. Install operator
2. Watch controller-manager OOM
Impact
Operator is unusable
Env
<Where was the bug found, i.e. OCP build, operator build, kata-containers build, cluster infra, test case id>
Additional helpful info
It OOMs after NodeCreate
2025-08-05T13:02:03Z INFO controllers.KataConfig.NodeCreate node created {"node name": "worker3"}
When I up the memory in the CSV for the deployment of controller-manager, the next lines are
2025-08-05T13:02:03Z INFO controllers.KataConfig.McpCreate MCP created {"MCP name": "kata-oc"}
2025-08-05T13:02:03Z INFO controllers.KataConfig.McpCreate MCP created {"MCP name": "master"}
2025-08-05T13:02:03Z INFO controllers.KataConfig.McpCreate MCP created {"MCP name": "worker"}
Also: Slack thread