Api is not compatible with Kubernetes NodePort network interfaces #1095

Closed
opened 8 months ago by jblevins1991 · 2 comments

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.
Owner

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)?
Owner

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

Closing this as I belive it has been solved, please ping if you're still having issues with it.
konrad closed this issue 24 hours ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/api#1095
Loading…
There is no content yet.