Automatic generation of nodePort now broken

Hi, since !246 (merged) has been merged we are getting problems that our applications are all trying to run on the now new default nodePort 30001. Previously it worked just fine using a random free port. Could you please look into this as this is breaking our CI in production environment.

our auto-deploy-values.yaml:

service:
  internalPort: 3000
  externalPort: 80
  type: "NodePort"
livenessProbe:
  path: "/health"
readinessProbe:
  path: "/health"
serviceAccount:
  createNew: "true"
  name: "app-name"
replicaCount: 1
ingress:
  annotations:
    kubernetes.io/ingress.class: "alb"
    alb.ingress.kubernetes.io/scheme: "internet-facing"
    alb.ingress.kubernetes.io/healthcheck-path: "/health"
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP":80}, {"HTTPS":443}]'
    alb.ingress.kubernetes.io/actions.ssl-redirect: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'

Regards Alex