Skip to content

[Backport release-1.3] fix(cluster-api): fix kamaji OOM and set limits on unset providers - #2710

Merged
myasnikovdaniil merged 1 commit into
release-1.3from
backport-2708-to-release-1.3
May 21, 2026
Merged

myasnikovdaniil merged 1 commit into
release-1.3from
backport-2708-to-release-1.3

Conversation

@github-actions

Copy link
Copy Markdown

Description

Backport of #2708 to release-1.3.

The kamaji control-plane-provider override in templates/providers.yaml
targeted containers[name=manager], but the upstream container is named
"controller". The CAPI operator merges container overrides by name, so
the intended cpu: 1 / memory: 1024Mi limits were silently dropped and
the upstream default of memory: 128Mi was used, producing repeated
OOMKilled restarts of the kamaji controller (exit code 137).

The other three providers (core, bootstrap, infraprovider/kubevirt)
ship upstream with no resources block and have no cozystack override,
so they run BestEffort and are first to evict under memory pressure.
Set modest limits (500m / 256Mi) and requests (10m / 64Mi) matching
typical CAPI controller-manager footprint.

Assisted-By: Claude <[email protected]>
Signed-off-by: Myasnikov Daniil <[email protected]>
(cherry picked from commit 6ae66f7)
@dosubot dosubot Bot added area/platform Issues or PRs related to platform infrastructure (bundle, flux, talos, installer) kind/backport Categorizes issue or PR as requiring a backport to the current release line kind/backport-previous Categorizes issue or PR as requiring a backport to the previous release line labels May 21, 2026
@myasnikovdaniil
myasnikovdaniil merged commit 6325221 into release-1.3 May 21, 2026
5 checks passed
@myasnikovdaniil
myasnikovdaniil deleted the backport-2708-to-release-1.3 branch May 21, 2026 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/platform Issues or PRs related to platform infrastructure (bundle, flux, talos, installer) kind/backport Categorizes issue or PR as requiring a backport to the current release line kind/backport-previous Categorizes issue or PR as requiring a backport to the previous release line

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant