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

This page summarizes the projects mentioned and recommended in the original post on reddit.com/r/kubernetes

Our great sponsors
  • SonarLint - Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
  • Scout APM - Less time debugging, more time building
  • OPS - Build and Run Open Source Unikernels
  • inlets-archived

    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

    Manage and Integration with your Kubernetes dev environment more efficient.

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

  • SonarLint

    Deliver Cleaner and Safer Code - Right in Your IDE of Choice!. SonarLint is a free and open source IDE extension that identifies and catches bugs and vulnerabilities as you code, directly in the IDE. Install from your favorite IDE marketplace today.

  • sshuttle

    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. (by sshuttle)

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

  • Nebula

    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

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts