Thanks for sharing this guide, one question while I had the VPN tunnel created without any issue and able to ping both interfaces, the kubernetes service in different namespace is not reachable from the client. I have Kibana service deployed in different namespace and exposed as node port but from the client I can't reach it. The kube-DNS is added for the PEERDNS but unable to get kibana UI. Is there any extra step I should check?
It could be for many reasons, for example: you don't have enabled the ip_forward in the server, you cluster have a network policy, your DNS is not resolving the service ip and so on. Try testing the cluster iyou directly with nmap and traceroute. For DNS you can test with this command: dig @server_ip fqdn_service_name.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for sharing this guide, one question while I had the VPN tunnel created without any issue and able to ping both interfaces, the kubernetes service in different namespace is not reachable from the client. I have Kibana service deployed in different namespace and exposed as node port but from the client I can't reach it. The kube-DNS is added for the PEERDNS but unable to get kibana UI. Is there any extra step I should check?
It could be for many reasons, for example: you don't have enabled the ip_forward in the server, you cluster have a network policy, your DNS is not resolving the service ip and so on. Try testing the cluster iyou directly with nmap and traceroute. For DNS you can test with this command: dig @server_ip fqdn_service_name.