Using newt in a k8s/k3s environment

[ModestTG]

Hello,

I'm very interested in the pangolin / newt system for a self-hostable alternative to something like CloudFlare tunnels. I currently have a k3s environment set up that is utilizing CF tunnels for external access to it's services. I have a general working knowledge of how k3s works, enough to host some stuff, but not enough to know how to port something like newt into my existing k3s enviroment and connecting it to a pangolin instance. What is the best approach to accomplish something like this?

• Do I just add newt as another container to my pods?
• Can I create an ingressclass somehow for newt to route everything appropriately?

Any help is appreciated. Thanks in advance!

[miloschwartz]

I have to admit I don't know enough about k3 to give a proper answer, but:

Do I just add newt as another container to my pods?

Newt can run as a container, so however you can provision a container for your environment and pass the credentials as variables, should work. Then you just need to make sure the Newt container can address the resource directly.

[ModestTG]

Thanks for the reply. Yeah I think I could accomplish that pretty easily. I'm sure there is a way to do something like ingress-nginx and make it cluster wide but that'll require more research from me

[marcschaeferger]

There is a Helm Chart for installing Newt tested with different OnPrem and Cloud Kubernetes Enviroments.
There are plans for a Kubernetes Operator that can be used to install Newt, Pangolin etc. as well but it's not released yet.

https://artifacthub.io/packages/helm/fosrl/newt
https://github.com/fosrl/helm-charts