[fix] Add default multiplayer ingress rule

[jjlgao]

Addresses #199, aims to automatically create an ingress rule, if multiplayer is enabled, to point requests for /api/multiplayer to the multiplayer pod. To avoid conflicts with folks who already have this ingress rule set, this automatic rule can be disabled using multiplayer.ingress.enabled=false.

Tested by applying to our test cluster, which created a new (inaccessible) ingress, which looks like this (redacted hostnames just in case, but they shouldn't be sensitive):

I also added these values to the values.yaml file:

ingress:
  enabled: true
  labels: {}
  annotations: {}
  # kubernetes.io/ingress.class: nginx
  # kubernetes.io/tls-acme: "true"
  hosts:
  - host: retool-dev.[hostname]
    paths:
      - path: /
  tls:
  - secretName: retool-dev-tls
    hosts:
      - retool-dev.[hostname]
  pathType: ImplementationSpecific
multiplayer:
  enabled: true

[lukefoster11]

Looks good, just had one question before merge

[lukefoster11]

I know this can be set to false but by default could this be a breaking change for anyone who has already set up this ingress rule?

[jjlgao]

It will be, which I considered and decided to keep this way. I think there's no real way to make this default-true moving forward, without breaking folks who have the ingress rule already. I believe that what will happen is that people will run into an error on helm upgrade due to the duplicate routes, so when I tag the release for this PR I'll make a note in the release to expect the breaking change.

[lukefoster11]

Gotcha, yeah don't know a smooth alternative so this makes sense

[alex-stabile]

The multiplayer service uses 3009 as the default port, should that be set here?

[jjlgao]

No, this points at the entry port for the service, which is 80: https://github.com/tryretool/retool-helm/blob/main/charts/retool/templates/deployment_multiplayer_ws.yaml#L13

The destination port for the multiplayer deployment is hardcoded to 3001 here (probably should have been left at 3009 rather than introducing potential port conflicts, but that isn't relevant for this change), with another hardcoded env var pointing the container to port 3001: https://github.com/tryretool/retool-helm/blob/main/charts/retool/templates/deployment_multiplayer_ws.yaml#L78