<p>I have a quick question on Kubernetes ingress. I have both Nginx ingress controller and AWS ALB ingress controller and ingress resources for both Nginx and AWS ALB in a single cluster. Both of these ingress resources are pointed to a single service and deployment file, meaning, bothe the ingress resources are pointed to the same service. However, when I hit the Nginx ingress URL, I'm able to see the desired page, but with the AWS ALB ingress, I can only see the apache default page. I know this doesn't sound practical, but I'm trying to test out something with both these ingress resources. Just wanted to understand, where am I missing out on seeing the application for AWS ALB ingress URL.</p>

Bhargav Mg
<p>Posting this community wiki answer to point that the issue to this question was resolved in the comments.</p>
<p>Feel free to edit and expand.</p>
<hr />
<p>The solution to the issue:</p>
<blockquote>
<p>AWS ALB <code>Ingress</code> was pointing to the default <code>apache</code> document root in the pod. <strong>I modified the document root to the application data</strong> and was able to see my application page open up!</p>
</blockquote>
<hr />
<p>Additional resources that could be useful in this particular example:</p>
<ul>
<li><em><a href="https://www.tecmint.com/change-root-directory-of-apache-web-server/" rel="nofollow noreferrer">Tecmint.com: Change root directory of a apache web server</a></em> - how to change the <code>apache2</code>: <code>DocumentRoot</code></li>
<li><em><a href="https://github.com/kubernetes-sigs/aws-load-balancer-controller/tree/main/docs/examples" rel="nofollow noreferrer">Github.com: Kubernetes sigs: AWS load balancer controller: Docs: Examples</a></em> - examples of <code>ALB</code> that satisfies <code>Ingress</code> resource.</li>
</ul>
