vpn

As my application nears production readiness, one of the key considerations is securely accessing internal Kubernetes services—such as databases and message brokers—from my local development machine. Initially, I configured TCP forwarding for these services on my ingress controller: tcp:"4222": nats/nats-cluster:4222"5432": pgo/astring-ha:5432"6379": redis/redis:6379"9042": scylla/scylla-client:9042While each service requires authentication, I’m still not fully comfortable exposing them directly to the public internet. Ideally, only HTTP endpoints (like my backend services or monitoring tools) should be publicly accessible, protected via basic auth or other mechanisms....