helm nodePort support

I have installed it with the following piece of values.yaml:

service:
  type: NodePort
  port: 12345
  nodePort: 31245

It accepted the type and port parameters but ignored the nodePort one, what put it in a random node port.

There is any other place where I can set the nodePort to a fixed port?

Also, don't know if it is related, when accessing it at the node port, it seems to be all working, with exception of any /settings/ path, witch is showing a page with the text:

Hello /settings!

and log:

│ tianji-7d98cf8fcb-pfcjr GET / 200 479 - 0.669 ms                                                                                                                               │
│ tianji-7d98cf8fcb-pfcjr GET /settings/profile 304 - - 0.981 ms                                                                                                                 │
│ tianji-7d98cf8fcb-pfcjr GET /assets/index-Rn2BNgmt.js 304 - - 0.429 ms                                                                                                         │
│ tianji-7d98cf8fcb-pfcjr GET /assets/index-vZMM8v6j.css 304 - - 0.622 ms                                                                                                        │
│ tianji-7d98cf8fcb-pfcjr GET /locales/en/translation.json 304 - - 1.025 ms                                                                                                      │
│ tianji-7d98cf8fcb-pfcjr GET /locales/pt-BR/translation.json 304 - - 4.524 ms                                                                                                   │
│ tianji-7d98cf8fcb-pfcjr GET /icon.svg 304 - - 2.531 ms                                                                                                                         │
│ tianji-7d98cf8fcb-pfcjr POST /trpc/user.loginWithToken?batch=1 200 - - 7.305 ms                                                                                                │
│ tianji-7d98cf8fcb-pfcjr GET /trpc/global.config?batch=1&input=%7B%7D 200 - - 0.390 ms                                                                                          │
│ tianji-7d98cf8fcb-pfcjr 2025-11-13 21:06:52.278 - info: [Socket] Authenticated via JWT: admin

I have to add postgress tag as well, because it wont find versioned tags at bitnami docker registry as is the Tianji chart default.

postgresql:
  enabled: true
  image:
    registry: docker.io
    repository: bitnami/postgresql
    tag: "latest"
    pullPolicy: IfNotPresent

Any ideas?

Start with the supplied values.yaml and compare service.type, port, and nodePort handling in the Helm chart. Reproduce the /settings behavior through the NodePort and check the PostgreSQL image tag configuration against the Bitnami registry. Done means the fixed NodePort is honored, /settings serves the application rather than “Hello /settings!”, and the configured PostgreSQL image resolves.