Thank you, John. Nice, concise explanation. It's an interesting pattern. It seems mildly inefficient in terms of container sprawl, though. I wonder if in the future container orchestration systems or the appropriate parts thereof could allow you to consolidate the sidecars. I'm torn, though. There's a lot good about this approach. EDIT: Nevermind. I guess if you have to have the sidecar proxies for your mesh my concern is moot.
Great points, Jared! It's fantastic that you are thinking through these things. While technology solves some (or many) problems, it can definitely introduce other issues/problems along the way. This is where you have to weigh your options and go with the best overall solution for what you are trying to solve. Container sprawl and Kubernetes complexity is certainly something to keep an eye on. Visibility and operability of this environment is becoming a huge point of interest...there are lots of moving pieces, and it's hard to watch it all and make intelligent business decisions based on all the activity happening in the cluster. Thanks again for the comment...we need people like you to bring up these points as we move forward!!
Hey, I want to make a sidecar container that will read all the traffic from the main container in order to maintain an automated API inventory, how do I suggest I move forward with this?
Thank you, John. Nice, concise explanation. It's an interesting pattern. It seems mildly inefficient in terms of container sprawl, though. I wonder if in the future container orchestration systems or the appropriate parts thereof could allow you to consolidate the sidecars. I'm torn, though. There's a lot good about this approach.
EDIT: Nevermind. I guess if you have to have the sidecar proxies for your mesh my concern is moot.
Great points, Jared! It's fantastic that you are thinking through these things. While technology solves some (or many) problems, it can definitely introduce other issues/problems along the way. This is where you have to weigh your options and go with the best overall solution for what you are trying to solve. Container sprawl and Kubernetes complexity is certainly something to keep an eye on. Visibility and operability of this environment is becoming a huge point of interest...there are lots of moving pieces, and it's hard to watch it all and make intelligent business decisions based on all the activity happening in the cluster. Thanks again for the comment...we need people like you to bring up these points as we move forward!!
great explanation thanks
We appreciate the comment!
Hey, I want to make a sidecar container that will read all the traffic from the main container in order to maintain an automated API inventory, how do I suggest I move forward with this?