Which method do you prefer for accessing your Kubernetes API Server within the Private Network?

• inlets-archived

  8 8,407 8.0 Go

  Discontinued Cloud Native Tunnel

  

I found some of them that are related to this topic, it might be useful for you too: * inlets * kt-connect * shuttle * ngrook

• kt-connect

  1 1,451 0.0 Go

  A toolkit for Integrating with your kubernetes dev environment more efficiently

  

I found some of them that are related to this topic, it might be useful for you too: * inlets * kt-connect * shuttle * ngrook

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• sshuttle

  39 11,094 7.9 Python

  Transparent proxy server that works as a poor man's VPN. Forwards over ssh. Doesn't require admin. Works with Linux and MacOS. Supports DNS tunneling.

  

I found some of them that are related to this topic, it might be useful for you too: * inlets * kt-connect * shuttle * ngrook

• Nebula

  140 13,717 8.6 Go

  A scalable overlay networking tool with a focus on performance, simplicity and security

  

Normally Wireguard or sshuttle, currently experimenting with https://github.com/slackhq/nebula going forward

Suggest a related project