github-starred/newt
2
0
Fork 0
mirror of https://github.com/fosrl/newt.git synced 2026-03-09 07:12:28 -05:00
Code Issues 21 Packages Projects Releases 25 Wiki Activity

[Feature Request] Container healthcheck #18

New Issue
Closed
opened 2025-11-19 07:12:00 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-19 07:12:00 -06:00
Owner
Copy Link

Originally created by @p3l1 on GitHub (Apr 20, 2025).

Hello there,

I am running this inside my kubernetes cluster at home and I would like newt to be high available on three different nodes, as it is responsible for connecting services into my homelab.

From what I've gathered, only one node is able to connect to gerbil at the same time. This is what I've expected.

I am not sure how easy a high availability setup on pangolin side woudl be.

What already would help is a container healthcheck like mentioned in https://github.com/fosrl/newt/issues/31. I could then tell kubernetes to create a new pod, when the healthcheck fails. Sometimes newt is not able to reconnect after a timeout and I have to restart the container manually.

Thanks for your great work on Pangolin and Newt! This tool is what I've been looking for, for a long time!

Originally created by @p3l1 on GitHub (Apr 20, 2025). Hello there, I am running this inside my kubernetes cluster at home and I would like newt to be high available on three different nodes, as it is responsible for connecting services into my homelab. From what I've gathered, only one node is able to connect to gerbil at the same time. This is what I've expected. I am not sure how easy a high availability setup on pangolin side woudl be. What already would help is a container [healthcheck](https://docs.docker.com/reference/dockerfile/#healthcheck) like mentioned in https://github.com/fosrl/newt/issues/31. I could then tell kubernetes to create a new pod, when the healthcheck fails. Sometimes newt is not able to reconnect after a timeout and I have to restart the container manually. Thanks for your great work on Pangolin and Newt! This tool is what I've been looking for, for a long time!
GiteaMirror commented 2025-11-19 07:12:01 -06:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Apr 22, 2025):

Hi! Thanks for your interest in our project!

A high availability pangolin is in development and we will release more information about that at some point. We are tracking that on the pangolin repo so I have changed the name to reflect the other request about the health checks would I think would be quite valuable. I think I will get to that sometime soon!

@oschwartz10612 commented on GitHub (Apr 22, 2025): Hi! Thanks for your interest in our project! A high availability pangolin is in development and we will release more information about that at some point. We are tracking that on the pangolin repo so I have changed the name to reflect the other request about the health checks would I think would be quite valuable. I think I will get to that sometime soon!
GiteaMirror commented 2025-11-19 07:12:01 -06:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Apr 22, 2025):

Sorry actually this is a duplicate of #31. I am going to close for now.

@oschwartz10612 commented on GitHub (Apr 22, 2025): Sorry actually this is a duplicate of #31. I am going to close for now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
good first issue
help wanted
Improvement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/newt#18
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?