vikunja/vikunja
5
48
Fork 86
Code Issues 150 Pull Requests 38 Packages Releases 37 Activity

Api is not compatible with Kubernetes NodePort network interfaces #1095

New Issue
Closed
opened 2022-01-20 21:19:42 +00:00 by jblevins1991 · 2 comments
jblevins1991 commented 2022-01-20 21:19:42 +00:00
Copy Link

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
Owner
Copy Link

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
Owner
Copy Link

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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
dependencies
duplicate
This issue or pull request already exists
help wanted
Need some help
invalid
Something is wrong
kind/bug
Something is not working
kind/feature
New feature
needs reproduction
question
More information is needed
security
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vikunja/vikunja#1095
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?