<p>I have a pod with 3 containers (ca, cb, cc).</p>
<p>This container is owned by TeamA. Team A creates and owns ca.the other two containers are developed by two other teams. TeamB for cb and TeamC for cc.</p>
<p>Both cb and cc also run independently (outside the TeamA pod) as services within this same cluster.</p>
<p>How can TeamA pod find out when cb or cc deploy a newer version in the cluster and how can we ensure that it triggers a refresh?</p>
<p>As you may have guesses cb and cc are services that ca relies on heavily and they are also services in their own right.</p>
<p>Is there a way to ensure that TeamA pod keeps cb and cc updated whenever TeamB and TeamC deploy new versions to the cluster?</p>

anuruddha kulatunga
<p>This is not a task for Kubernetes. You should configure that in your CI/CD tool. For example, whenever a new commit is pushed to service A, it will first trigger the pipeline for A, and then trigger corresponding pipelines for services B and C. Every popular CI/CD system has this ability and this is how it's normally done.</p>
<p>Proper CI/CD tests will also protect you from mistakes. If service A update breaks compatibility with B and C, your pipeline should fail and notify you about that.</p>
