Api is not compatible with Kubernetes NodePort network interfaces #1095

New Issue

jblevins1991 · 2022-01-20T21:19:42Z

jblevins1991 commented

2022-01-20 21:19:42 +00:00

Description

The lack of this environment variable, VIKUNJA_DATABASE_PORT makes it impossible to use the backend in a kubernetes environment using NodePort, as the NodePort specification only allows allocation and exposure of ports 30000-32768 to the outside world. The api has port 3306 hardcoded.

Proposed Solution

Add an environment variable named VIKUNJA_DATABASE_PORT in the docker image to allow the user to specify which port, the database server can be found at. This environment variable would be substituted in the database connection implementation functionality.

## Description The lack of this environment variable, `VIKUNJA_DATABASE_PORT` makes it impossible to use the backend in a kubernetes environment using `NodePort`, as the NodePort specification only allows allocation and exposure of ports `30000-32768` to the outside world. The api has port `3306` hardcoded. ### Proposed Solution Add an environment variable named `VIKUNJA_DATABASE_PORT` in the docker image to allow the user to specify which port, the database server can be found at. This environment variable would be substituted in the database connection implementation functionality.

konrad commented

2022-01-20 22:30:08 +00:00

Did you try specifying the port as part of the db host?

Did you try specifying the port as part of the [db host](https://vikunja.io/docs/config-options/#host)?

konrad commented

2022-10-01 15:18:52 +00:00

Closing this as I belive it has been solved, please ping if you're still having issues with it.

konrad closed this issue

2022-10-01 15:18:52 +00:00

konrad referenced this issue from a commit

2024-02-07 14:00:29 +00:00

chore(deps): update dependency esbuild to v0.14.0 (#1095)