@Rocky when starrocks 4.1.1 will be released that fix be pod bug

The "BE pod bug" you are referring to is likely the unstable load order issue identified in the StarRocks v4.1.0 container image. This issue causes BE (Backend) processes to fail to start reliably in containerized environments like Kubernetes. Current Status and Fix * Fix Version: The fix for this issue is tracked under GitHub issue #71825 and is officially slated for the StarRocks 4.1.1 release. * Release Date: As of late May 2026, version 4.1.1 has not yet been publicly released. * StarRocks 4.1.0 was released on April 13, 2026. * Patch versions typically follow a 2–3 week cycle. Given that official documentation and community posts as late as May 19th were still advising users to "wait for v4.1.1," the release is likely imminent. Recommendations * Do Not Upgrade to 4.1.0: If you are running StarRocks in a container/Kubernetes environment, the official documentation explicitly warns not to upgrade to v4.1.0. * Wait for 4.1.1: Stay on your current stable version (such as 4.0.x or 3.x) until 4.1.1 is officially available on the StarRocks GitHub Releases page or Docker Hub. * Check Slack: For a more precise "to-the-day" update, I recommend checking the

#questions-and-troubleshooting

channel in the StarRocks Community Slack, where maintainers often provide real-time updates on patch availability.

I think it would be important to release the patch sooner than later. We've hit the same issue.