Defend for Containers deprecation

I’m really frustrated with Elastic’s decision to deprecate Defend for Containers starting with Elastic Stack 9.0. Now, with no clear or feature-complete replacement, users are left scrambling to fill the gap. It’s a big step backward at a time when container security adoption is only growing.

If container security is truly a priority for Elastic and its customers, this should have been handled much better. Users deserve clearer communication, backward compatibility, and fully functional, supported alternatives instead of sudden deprecations that cause operational headaches.

I hope Elastic reconsiders this or at least provides comprehensive tools and documentation soon for a smooth transition. Moreover im hoping Elastic will acquire at least one company that truly understand containers and their critical role in modern cloud-native infrastructure.

Hopefully, Elastic takes this community input seriously.

Thank you

Hi @Lexinga, thanks for reaching out. We understand your frustration regarding this deprecation, and we apologize for the operational headaches this has caused. Your feedback is important, and we're taking it very seriously.

Protecting and monitoring Kubernetes environments is a top priority for us. We know this is a critical need for many of our users, and we're actively working on a long-term solution. While we can't share specific details at this moment, we are committed to providing a robust and comprehensive approach to container security.

We'll be sure to provide more information as soon as we can. We appreciate your patience and your dedication to the Elastic community.