How to connect a company's private network via VPN to cloud Kubernates?

Question

openvpn

Hello!

Attention! The question is not access to the cuber, but vice versa - from the cuber to another network, reliably, fault-tolerant.

We have:
- a private network, closing from the outside
- a configured openvpn
- Managed Kubernates in the cloud without access to the virtual machine console

Is it possible to somehow stably connect the private network with the cuber so that I can more or less simply access the ports of the machines inside it. The ssh tunnel with port forwarding did not work - it's not convenient, some scraps remain in the console on the servers. I thought that I could somehow raise pods with openvpn with port forwarding?

Tell me what are the options?

UPD. So far, I had to raise an openvpn client in each pod and get all the resources of the company's private network into the pod network. This doesn't seem like the best option to me, as having to keep vpn connections in every pod seems redundant. But you don’t need to do any port forwarding, since in theory I would have to throw about 20-30 ports from different machines into the cuber as local resources.

Answer 1

Well, skip OpenVPN and go to your cuber. Quite an option.

Answer 2

If kubernetes is published on an external address, then you can use the port-forward feature of the kubectl utility. Further, it is easy to climb inside the cluster and feel the services in it, as if they were directly accessible.
In general - first you need to answer the question WHY you need access to the cluster - for developers (ad-hoc tasks like testing, configuration) or to ensure the connectivity of services in kubernetes and in the office network