<p>I have one service called "workspace-service-b6" which is running on port 5000, See the below ingress file. Now I want to serve the static content on the same service (workspace-service-b6) by adding the path route.</p>

<p>Example:- Service is working on <a href="https://workspace-b6.dev.example.com" rel="nofollow noreferrer">https://workspace-b6.dev.example.com</a></p>

<p>Now if the user adds  "/workspace/v2/ "at the end of the URL.</p>

<p>Like this:- <a href="https://workspace-b6.dev.example.com" rel="nofollow noreferrer">https://workspace-b6.dev.example.com</a><strong>/workspace/v2/</strong> it will redirect to s3 bucket "<a href="https://s3.console/buckets/xyz/abc/build" rel="nofollow noreferrer">https://s3.console/buckets/xyz/abc/build</a>" where my static content is available.</p>

<p>My Ingress file :-</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: b6-ingress 
namespace: b6
annotations:
kubernetes.io/ingress.class: "nginx"
kubernetes.io/tls-acme: "true"
spec:
tls:
- hosts:
- workspace-b6.dev.example.com
secretName: xyz-crt
rules:
- host: workspace-b6.dev.example.com
http:
paths:
- backend:
serviceName: workspace-service-b6
service port: 5000
</code></pre>

me25
<p>While it’s kind of possible, the real answer is “don’t”. The ingress system is just a proxy, set up separate pods for content.</p>
