Igor Soares 3c9a6fbfe8 Clean up failed builder pods on restore
It was identified that KMM may start builder pods before coredns pods
are fully running during a platform restore. This results in an error
when pushing module images to the local registry, since the address
cannot be resolved.

This commit aims to clean up the failed pods once restore is fully
completed so that the operator can spawn new builder pods.

Test plan
PASS: build-pkgs && build-image.
PASS: Deploy a module with failing build steps.
      Call the restore lifecycle.
      Confirm that failed builder pods were removed and that new ones
      were spawned.
PASS: Run backup and restore on AIO+ with KMM and deployed modules.
PASS: Remove KMM app.

Change-Id: I0e7229a63c89e5c235fe856a5fed5acd264b27aa
Signed-off-by: Igor Soares <Igor.PiresSoares@windriver.com>
2026-03-02 19:34:46 -03:00
2026-01-22 17:01:29 -03:00
2025-12-01 17:42:47 -03:00
2026-01-22 17:01:29 -03:00

app-kernel-module-management

App-kernel-module-management fluxCD app

About app-kernel-module-management

KMM (Kernel Module Management) is a Kubernetes Operator that allows for the compilation and install of out-of-tree Linux Kernel modules.

Upstream project

Kernel Module Management on Github

Description
StarlingX Kernel Module Manager App
Readme 430 KiB
Languages
Python 62.7%
Makefile 17.3%
Dockerfile 11.8%
Shell 6.1%
C 1.7%
Other 0.4%