Yeah, that is pretty close to what I have. First, check if you can ping the nodes from your external client. If not, ensure that Netmaker Server is set up as the ingress gateway. From that you should be able to ping the nodes over your netmaker network. Then you need to have the egress gateway inside the cluster. It's another netclient that you install on one of your k8s nodes that's specifically designated as the gateway. It routes traffic inside the cluster from your ext clients. There is an example deployment in the repo. Then you have to label the node and mark it as the gateway using kubectl. Then you also have to mark it as the gateway in Netmaker UI. After all that is set up you need to somehow expose whatever service (Wordpress in your case). You can do it using a Nodeport but the proper way is to keep your wordpress service as a clusterIP and an ingress. Sounds like it could be traefik in your case. I actually have two ingresses in my cluster, one for public traffic and one for private traffic. Public is handled by ambassador and i have a dead simple nginx-ingress for the road warrior traffic. Helps me keep separation of concerns plus I don't need to pay for another loadbalancer. Either way once your ingress is set up to expose routes you can start routing. If you have DNS set up on Netmaker it's super simple - you just create the dns entry for a given route in Netmaker, say wordpress1.internal, and specify wordpress1.internal as the host in your traefik ingress config. The IP for the DNS is the cluster gateway IP (the IP of the cluster node that you labeled with kubectl earlier). Without DNS I suppose you would just use the IP of the gateway plus some sub url route e.g. 10.11.12.2/wordpress1. Not as clean but it would work