Reputation: 337
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.
Upvotes: 0
Views: 1412
Reputation: 9905
Posting this community wiki answer to point that the issue to this question was resolved in the comments.
Feel free to edit and expand.
The solution to the issue:
AWS ALB
Ingress
was pointing to the defaultapache
document root in the pod. I modified the document root to the application data and was able to see my application page open up!
Additional resources that could be useful in this particular example:
apache2
: DocumentRoot
ALB
that satisfies Ingress
resource.Upvotes: 1