Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NodePort mode adds port to host header rule, but shouldn't #552

Closed
nhumrich opened this issue Sep 29, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@nhumrich
Copy link

commented Sep 29, 2017

I am using NodePort mode, so that I can point my own ALB at HAProxy. Using NodePort, I correctly get a service on node port 31485.

In my ingress, I have host based routing, for example foo.bar.com goes to my web-gateway. The rule in haproxy configuration shows up as:

acl host_acl_web-gateway.default:80-bp7jkb hdr(host) -i foo.bar.com:31485

As you can see, its adding the node port at the end. Which means that routing doesnt actually work correctly.

Is there anyway to remove the nodeport in the host routing?

@tamalsaha

This comment has been minimized.

Copy link
Member

commented Oct 3, 2017

This is done, since the expectation is that with NodePort mode (usually in bare metal cluster), NodePorts are used by external clients. Since you are using a manually manged ALB, this is causing problem. We are going to add the following annotation that you can apply to disable this behavior in next release (4.0.0):
ingress.appscode.com/force-service-port: true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.