Kubernetes Side-Car Container Challenges

side cards seems really easy, one of the challenges that we have seen or the ecosystem has seen is the over provisioning of resources. So this resulted in a lot of over provision resources, a lot of waste when it comes to the CPU and memory that is needed by your application from your community's clusters. I think more challenges include things like the side-car upgrade requires restarting of application; any new functionality that gets introduced in your side-cars needs a restart of your application itself. And just the overall complexity, right? You're adding, especially from a troubleshooting and maintenance, you now have literally double the amount of containers to potentially monitor and trouble-shoot if something goes wrong