search

kubernetes / ingress-nginx

Ingress NGINX Controller for Kubernetes
https://kubernetes.github.io/ingress-nginx/
Apache License 2.0
17.42k stars 8.24k forks source link

Redirect failing for all SOAP API Calls in ingress LB #3963

Closed premrupali closed 5 years ago

premrupali commented 5 years ago

Is this a request for help?

NGINX Ingress controller version: nginx/1.13.9

Kubernetes version (use kubectl version): Kubernetes build is 17.03 Client Version: v1.9.6 Server Version: v1.10.11 Docker 18.06.0-ce.

Environment: Test

What happened:

I have setup my app using company private cloud and using ingress control to expose my service. Every thing works as expected. To do performance test, i redirect all live preprod traffic from existing VIP (.i.e. test.pp.companydomain.com --> k8.companydomain.com.
now i see issue here.

Client application is still hitting test.pp url and it is working for all restful api calls. but if they use soap call it is failing giving error in my k8s app . non-sopa request.

funny thing now. if i use postman or soapui call to call same service using test.pp domain, it works. if i call my k8s vip it works. only it doesn't it call comes thru application.

What you expected to happen:

Soap call should work same as restful call using redirect.

How to reproduce it (as minimally and precisely as possible):

by redirect and call soap api thru exiting LB --> redirect --> new K8s VIP --> K8s application.

Anything else we need to know: My application is CA API Gateway (Layer 7) which i am setting up in K8s. It is security gateway.
Not sure any header is getting lost in transition. if so what setting i should use in my yaml file.

here is the sample yaml.

apiVersion: extensions/v1beta1 kind: Ingress metadata: name: gw-onlineservices-GATEWAY_ENV namespace: NAMESPACE annotations: kubernetes.io/ingress.class: "nginx" nginx.ingress.kubernetes.io/secure-backends: "true" nginx.ingress.kubernetes.io/proxy-read-timeout: "600" spec: tls:

fejta-bot commented 5 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot commented 5 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

fejta-bot commented 5 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close

k8s-ci-robot commented 5 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes/ingress-nginx/issues/3963#issuecomment-526969517): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.