You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The golink binary uses tsnet internally to connect to the tailnet. Is there a way to hook up a HEALTHCHECK to return the status of the golink binary’s internal tsnet connection? That sounds tricky now that I write it, but it would be pretty cool if the Docker health status could reflect the tailnet connection status.
The text was updated successfully, but these errors were encountered:
we could certainly add a health check endpoint, but does it make sense to have it report on the tsnet connection? By default, golink only listens on the tsnet connection, so the fact that you could even reach the healthcheck endpoint at all indicates that it's working. Or were you thinking the healthcheck would listen on a different interface?
I’m not referring to a “health check” as a general concept, but HEALTHCHECK the Docker feature; see https://scoutapm.com/blog/how-to-use-docker-healthcheck. This wouldn’t be going through the tsnet connection; this would be a feature of the Docker container.
The
golink
binary usestsnet
internally to connect to the tailnet. Is there a way to hook up aHEALTHCHECK
to return the status of thegolink
binary’s internaltsnet
connection? That sounds tricky now that I write it, but it would be pretty cool if the Docker health status could reflect the tailnet connection status.The text was updated successfully, but these errors were encountered: