helm deployment with `traefik.service.type=ClusterIP` fails

What happened:

When I specify “ClusterIP” for the service type I get the error:

Unable to deploy helm chart: cannot patch "traefik-dask-gateway" with kind Service: Service "traefik-dask-gateway" is invalid: spec.ports[0].nodePort: Forbidden: may not be used when `type` is 'ClusterIP'

What you expected to happen:

Able to deploy with ClusterIP

Minimal Complete Verifiable Example:

Should be simple to recreate

Anything else we need to know?:

I would like to use dask-gateway with port forwarding for testing, until I get openid authentication figured out. In any case I probably would like to deploy behind ingress-nginx and do tls-termination there (with letsencrypt provided by cert-manager).

Environment:

• cluster: EKS
• Dask version: dask-gateway 0.8.0 (latest chart)
• Python version:
• Operating System:
• Install method (conda, pip, source): helm

helm version
version.BuildInfo{Version:"v3.0.1", GitCommit:"7c22ef9ce89e0ebeb7125ba2ebf7d421f3e82ffa", GitTreeState:"clean", GoVersion:"go1.13.4"}

[shaunc]

Ah cool – so with this in values.yaml:

      traefik:
        service:
          type: ClusterIP
          ports:
            web:
              nodePort: null
            tcp:
              nodePort: null

It deploys! 👍

NAME                           TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
service/api-dask-gateway       ClusterIP   172.20.66.129   <none>        8000/TCP   16h
service/traefik-dask-gateway   ClusterIP   172.20.129.93   <none>        80/TCP     19s

so that’s one half of the problem. Presumably just putting those nodePort settings as defaults in values.yaml should do the trick. [A confirmation about how to deploy a custom authenticator would be appreciated.]

[jcrist]

Fixed by #305.