<p>I have several image do different thing. Now, I expose them like these commands:</p>
<pre><code>kubectl create deployment work_deployment_1 --image=username/work_image_1:0.0.1-SNAPSHOT
kubectl expose deployment work_deployment_1 --type=LoadBalancer --port=8000
</code></pre>
<p>and then</p>
<pre><code>kubectl create deployment work_deployment_2 --image=username/work_image_2:0.0.1-SNAPSHOT
kubectl expose deployment work_deployment_2 --type=LoadBalancer --port=9000
</code></pre>
<p>After deployment creating and exposing, I check them by <code>kubectl get service</code>, the result of it will like:</p>
<pre><code>NAME                   TYPE           CLUSTER-IP       EXTERNAL-IP      PORT(S)          AGE
work_deployment_1      LoadBalancer   10.245.197.226   159.65.210.104   8000:30798/TCP   30m
work_deployment_2      LoadBalancer   10.245.168.156   159.65.129.201   9000:32105/TCP   51s
</code></pre>
<p>Can I make deployment (or deployments), expose <code>same_external-ip:8000</code> and <code>same_external-ip:9000</code>, instead of address above (<code>159.65.210.104:8000</code> and <code>159.65.129.201:9000</code>) ?</p>

hlx
<p>You will need to have an Ingress controller installed in your cluster to handle incoming traffic and route it to the appropriate service. Examples of Ingress controllers include Nginx Ingress, Traefik, and Istio.</p>
<p>Another way around that we use in Azure and Google Cloud is that we Expose the services via App Gateway in Azure &amp; HTTPS Global LB</p>
<p>In GCP case and the services are exposed on the LB single Anycast IP.</p>
<p>In GCP Case workflow is:
<em>Create a Kubernetes service&gt; Create a backend service that references each Kubernetes service &gt; Create a URL map that maps the incoming requests to the appropriate backend service based on the requested URL or hostname &gt; Create a target HTTP proxy that references the URL map &gt; Create a Google Cloud HTTPS load balancer and configure it to use the target HTTP proxy</em></p>
<p>Each time the Front End will be using the SAME Anycast IP &amp; Different ports in front end...</p>
<p>In your private cloud case I will refer using Traefik you can follow their documentation on this:<a href="https://doc.traefik.io/traefik/providers/kubernetes-ingress/" rel="nofollow noreferrer">https://doc.traefik.io/traefik/providers/kubernetes-ingress/</a></p>
