osx Kubernetes kube-vpnkit-forwarder keep starting and Can't ping CLUSTER-IP

1. It seems to me your kube-vpnkit-forwarder works as expected... The log entry staring kube-vpnkit-forwarder doesnt mean it hasnt started itself. Instead, it means you dont have any resources vpnkit should automatically expose.

From officials, LoadBalancer and NodePort services automatically exposed on the host with a VPNKit controller

99,999% it will show you log entries as soon as you expose your pod/deployment with nodeport or LoadBalancer type.

2. Can't ping the CLUSTER-IP

Thats expected. The default Kubernetes ServiceType is ClusterIp, which exposes the Service on a cluster-internal IP. To reach the ClusterIp from an external computer, you can open a Kubernetes proxy between the external computer and the cluster.

Accessing services running on the cluster

Publishing Services (ServiceTypes)