<p>In K8S, the below creates a deployment with n replicas -<br />
<code>$ kubectl run nginx --imaage nginx --replicas 6 </code></p>
<p>But how can these replicas be accessed in a load balanced way as they don't have any common entry point (like service wrapped around them).</p>
<p>So what is the purpose of deployments being able to scale <strong>OR</strong> how can they be accessed in a load balanced fashion (without a service wrapped over deployment).</p>

<p><strong>Replicas</strong></p>
<p><code>.spec.replicas</code> is an optional field that specifies the number of desired Pods. It defaults to 1. and which will help replicaset to manage pods and desired number of pods should be available no matter what kubernetes controller-manager will take care of that.</p>
<p>Well if you are running deployment without service then it does not make any sense, no matter what you scale for 1 replicas or 6. If your create service and map to your deployment then kubernetes will take care of load balancing between pods. For more info please check this section of docs <a href="https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies</a></p>
