-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade to 4.9.0 results in plugin capability used before init: k8s meta #752
Comments
We're experiencing the same behavior and rollbacked chart version back to |
@jemag, @CarpathianUA it's a regression introduced in Falco 0.39.0. We are working on the fix and will release a patch as soon as possible. Thanks for reporting the bug. |
Hi!
Since it is null, you can just remove the line or keep it |
The fix is up! falcosecurity/falco#3368 |
@FedeDP That null is being generated by the chart itself. If indeed it should be removed or kept as "", then it would make sense to make those adjustments in how the chart renders the |
Well i'd just comment out also the |
This issue has been fixed in falco |
/close |
@alacuku: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Describe the bug
Upgrading the chart from 4.8.3 to 4.9.0 without any change to our values.yaml, there appear to now be a schema validation error:
Here is our plugins section from the falco configmap
This eventually result (not 100% sure if related) in the pod terminating with the following error:
Thu Oct 3 16:38:28 2024: Runtime error: plugin capability used before init: k8smeta. Exiting.
How to reproduce it
Deploy helm chart 4.9.0 with following values:
Expected behaviour
Falco runs normally just as in 4.8.3
Screenshots
Environment
cannot run command with crashlooping container, image
falco-no-driver:0.39.0
cannot run command with crashlooping container, hope this is sufficient;:
Linux version 5.15.164.1-1.cm2 (root@CBL-Mariner) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP
Cloud provider or hardware configuration:
Azure AKS
OS:
NAME="Common Base Linux Mariner"
VERSION="2.0.20240829"
ID=mariner
VERSION_ID="2.0"
PRETTY_NAME="CBL-Mariner/Linux"
ANSI_COLOR="1;34"
HOME_URL="https://aka.ms/cbl-mariner"
BUG_REPORT_URL="https://aka.ms/cbl-mariner"
SUPPORT_URL="https://aka.ms/cbl-mariner"
Kernel:
Linux aks-main-14571596-vmss000008 5.15.164.1-1.cm2 Pull falco chart from helm/charts #1 SMP Sun Aug 18 19:16:21 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
-helm chart 4.9.0
Additional context
Full logs before crash
The text was updated successfully, but these errors were encountered: