Skip to content

Conversation

wojcik91
Copy link
Contributor

@wojcik91 wojcik91 commented Sep 26, 2025

Closes #98

@wojcik91 wojcik91 requested a review from moubctez September 26, 2025 14:52
@wojcik91 wojcik91 self-assigned this Sep 26, 2025
- port: {{ .Values.service.grpc.port }}
targetPort: grpc
protocol: UDP
protocol: TCP
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isnt this supposed to be UDP? I thought it was the actual wireguard VPN connection.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this should indeed remain as UDP, but the service should be renamed to avoid confusion

@jseiser
Copy link

jseiser commented Sep 26, 2025

@wojcik91

In reading this, I think there is going to be a problem running in AWS atleast. The service would need configured to be exposed as an NLB. Which is not a problem. The issue though, is the NLB would need a way to determine that the POD is healthy, and you can not do a UDP health check, so it would expect some TCP/HTTP port/path that could it hit to actually decide the pod is able to have traffic routed to it.

moubctez
moubctez previously approved these changes Sep 29, 2025
@wojcik91 wojcik91 merged commit 2cb7eb3 into main Sep 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix invalid value references in helm charts
3 participants