kubernetes/minikube

add falco back to the new iso

Open

#22298 opened on Dec 22, 2025

View on GitHub
 (4 comments) (1 reaction) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
help wantedkind/featurepriority/backlog

Description

we removed falco in https://github.com/kubernetes/minikube/pull/20720/changes/4ef9e5160cfffeff678e8c285f42d64142ea8c73 also we removed sysdig needed by falco here https://github.com/kubernetes/minikube/pull/22290

if any developer search for falco on minikube, this task is available to work on as Nice to have !

Contributor guide

Tech stack
go
Domain
securityinfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with minikube build systemUnderstanding of falco and sysdigAbility to navigate Git history
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Review the referenced PRs #20720 and #22290 to understand the removal of falco and sysdig. Identify the ISO build configuration files (likely in the hack/ or images/ directory) where falco was included. Then re add falco and its dependency sysdig by reverting the relevant changes. Ensure the build process works correctly and test the new ISO.