Add value to specify nodePort

Question

Add value to specify nodePort

uqix opened this issue 2 years ago · 9 comments

Answer 1 · 2022-08-09T01:48:29.000Z

I'm not sure exactly what you're asking. We support using a nodePort service type to front the varnish pods if that's to what you're referring. You can set the service.type as described here. You can specify the port as well.

Answer 2 · 2022-08-09T02:33:58.000Z

Sorry for not being clear, I mean after setting service.type to NodePort we need to specify the port like 30000 instead of randomly(32124) allocated by k8s.

Answer 3 · 2022-08-09T03:27:05.000Z

No worries @uqix. Is the service.port config not working? We may have a bug. @tomashibm maybe you will be able to get to this before I will. If not, np I'll take a look when I can. Thanks!

Answer 4 · 2022-08-09T03:31:52.000Z

My config:

  service:
    type: NodePort
    port: 80
    # nodePort: 30000

I think service.port is bound to clusterIP, maybe a separate option is needed?

Answer 5 · 2022-08-09T08:07:17.000Z

See what you mean @uqix . @cin not a bug, just a config we need to expose. I guess @uqix you're hitting your k8s nodes directly from outside and that's why you need control over which port you open there for Varnish, right?

Besides nodeport for Varnish do you also need the same for the metrics port?

Answer 6 · 2022-08-09T09:01:55.000Z

@tomashibm exactly as you said,

first we allocate nodePorts manually to avoid conflicts, so better support specifying nodePort for all three ports(varnish/controller/metric)
second we use nodePort for external cloud LB

thanks

Answer 7 · 2022-08-16T09:29:25.000Z

@uqix which k8s version you're running on? we want to include a change that drops support for k8s 1.20<=. If you're using and older we'll do separate releases for these two changes

Answer 8 · 2022-08-16T09:37:09.000Z

We use v1.24, thanks

Answer 9 · 2022-08-17T18:04:50.000Z

released in the latest version @uqix