<p>If I have a service that is running on a cluster, can I deploy and add some new pods to the service dynamically?</p>

<p>For instance, if the service has the label "app=MyApp", can the new created pods with the same label "app=MyApp" be managed by the service?</p>

<p>Short answer - yes. And this is exactly what a kubernetes <a href="https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/" rel="nofollow noreferrer">replicaSet</a> enables, and these days you're most often encouraged to create one of those through a <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment/" rel="nofollow noreferrer">Deployment</a>. Once created, you can scale up (or down) and the service will dynamically update it's internal forwarding based on the state of the pod's response to "Ready" (see the <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/" rel="nofollow noreferrer">docs for a readiness probe</a>).</p>

<p>The <a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/" rel="nofollow noreferrer">label/selector mechanism</a> that you're describing is exactly how that works within Kubernetes in a variety of places, and service &lt;-> Pods that match is one of the most common</p>
