<p>I have setup Kubernetes cluster on Ubuntu Virtual Machines using the Vagrant and Oracle VirtualBox. I have created 3 node cluster i.e. 1 master and 2 worker nodes. I can connect to these nodes successfully and can run the kubectl commands.</p>
<p>I'm running these VM's on my laptop where the host machine is Mac OS. Now, I want to access the same Kubernetes cluster and run kubectl commands on my Mac Terminal.</p>
<p><strong>Following is my Vagrant file:-</strong></p>
<pre><code># -*- mode: ruby -*-
# vi:set ft=ruby sw=2 ts=2 sts=2:

# Define the number of master and worker nodes
# If this number is changed, remember to update setup-hosts.sh script with the new hosts IP details in /etc/hosts of each VM.
NUM_MASTER_NODE = 1
NUM_WORKER_NODE = 2

IP_NW = &quot;192.168.56.&quot;
MASTER_IP_START = 1
NODE_IP_START = 2
LB_IP_START = 30

# All Vagrant configuration is done below. The &quot;2&quot; in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(&quot;2&quot;) do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://vagrantcloud.com/search.
  # config.vm.box = &quot;base&quot;
  config.vm.box = &quot;ubuntu/bionic64&quot;

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  config.vm.box_check_update = false

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network &quot;public_network&quot;
  #config.vm.network &quot;private_network&quot;, ip: &quot;55.55.55.5&quot;
  #config.vm.network &quot;private_network&quot;, type: &quot;dhcp&quot;
  #config.vm.network &quot;public_network&quot;, :bridge =&gt; &quot;en0: Wi-Fi (Wireless)&quot;, :ip =&gt; &quot;192.168.56.2&quot;
  #config.vm.network &quot;public_network&quot;, :bridge =&gt; &quot;en0: Wi-Fi (Wireless)&quot;, type: &quot;dhcp&quot;

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder &quot;../data&quot;, &quot;/vagrant_data&quot;

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider &quot;virtualbox&quot; do |vb|
  #   # Customize the amount of memory on the VM:
  #   vb.memory = &quot;1024&quot;
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Provision Master Nodes
  (1..NUM_MASTER_NODE).each do |i|
      config.vm.define &quot;kubemaster&quot; do |node|
        # Name shown in the GUI
        node.vm.provider &quot;virtualbox&quot; do |vb|
            vb.name = &quot;kubemaster&quot;
            vb.memory = 2048
            vb.cpus = 2
        end
        node.vm.hostname = &quot;kubemaster&quot;
        node.vm.network :private_network, ip: IP_NW + &quot;#{MASTER_IP_START + i}&quot;
        node.vm.network &quot;forwarded_port&quot;, guest: 22, host: &quot;#{2710 + i}&quot;

        node.vm.provision &quot;setup-hosts&quot;, :type =&gt; &quot;shell&quot;, :path =&gt; &quot;ubuntu/vagrant/setup-hosts.sh&quot; do |s|
          s.args = [&quot;enp0s8&quot;]
        end

        node.vm.provision &quot;setup-dns&quot;, type: &quot;shell&quot;, :path =&gt; &quot;ubuntu/update-dns.sh&quot;

      end
  end


  # Provision Worker Nodes
  (1..NUM_WORKER_NODE).each do |i|
    config.vm.define &quot;kubenode0#{i}&quot; do |node|
        node.vm.provider &quot;virtualbox&quot; do |vb|
            vb.name = &quot;kubenode0#{i}&quot;
            vb.memory = 2048
            vb.cpus = 2
        end
        node.vm.hostname = &quot;kubenode0#{i}&quot;
        node.vm.network :private_network, ip: IP_NW + &quot;#{NODE_IP_START + i}&quot;
                node.vm.network &quot;forwarded_port&quot;, guest: 22, host: &quot;#{2720 + i}&quot;

        node.vm.provision &quot;setup-hosts&quot;, :type =&gt; &quot;shell&quot;, :path =&gt; &quot;ubuntu/vagrant/setup-hosts.sh&quot; do |s|
          s.args = [&quot;enp0s8&quot;]
        end

        node.vm.provision &quot;setup-dns&quot;, type: &quot;shell&quot;, :path =&gt; &quot;ubuntu/update-dns.sh&quot;
    end
  end
end
</code></pre>
<p>The IP address of my Host machine is 192.168.1.5 whereas for Kubernetes, these are 192.168.56.2, 192.168.56.3 and 192.168.56.4 for master, worker1 and worker2 nodes respectively.</p>
<p>I tried a lot but did not find any concrete solution. Would really appreciate your suggestions on this. Thanks</p>

vinod827
<p>Using <code>kubeconfig</code> file is standard way to interact with a kubernetes cluster from outside the cluster. So there is nothing wrong with that. From security standpoint it's not a good idea to use admin user credential in a <code>kubeconfig</code> file. To avoid that you can generate a service account token and use that in the <code>kubeconfig</code> file. Limit the privilege of the service account using appropriate <code>Role</code> and <code>RoleBinding</code>.</p>
<p>Check this to know how to create a kubeconfig with a service account token</p>
<p><a href="https://stackoverflow.com/questions/47770676/how-to-create-a-kubectl-config-file-for-serviceaccount">How to create a kubectl config file for serviceaccount</a></p>
