🤖 Generated by the Agentic Engineer
Problem
Kubescape's node-agent host sensor reports a warning on each sensing interval when kube-proxy is deliberately absent because the cluster uses Cilium kube-proxy replacement. Current upstream always runs the KubeProxyInfo sensor when host sensing is enabled and provides no per-sensor exclusion.
Disabling the complete host sensor would also remove useful OS, kernel, kubelet, open-port, hardening, and CNI evidence, so the platform should retain coverage while tracking a narrow compatibility fix.
Upstream: kubescape/node-agent#962
Acceptance criteria
- Keep Kubescape host-security sensing enabled.
- Consume an upstream release that treats absent kube-proxy as supported or exposes a per-sensor exclusion.
- Verify node-agent logs remain free of the KubeProxyInfo warning for more than one sensing interval.
- Verify the other host-sensor custom resources continue updating.
- Confirm Coroot no longer reports the recurring warning.
Problem
Kubescape's node-agent host sensor reports a warning on each sensing interval when kube-proxy is deliberately absent because the cluster uses Cilium kube-proxy replacement. Current upstream always runs the KubeProxyInfo sensor when host sensing is enabled and provides no per-sensor exclusion.
Disabling the complete host sensor would also remove useful OS, kernel, kubelet, open-port, hardening, and CNI evidence, so the platform should retain coverage while tracking a narrow compatibility fix.
Upstream: kubescape/node-agent#962
Acceptance criteria