如何从主机访问 Kubernetes 集群?

How can I access the Kubernetes Cluster from Host machine?

我已经使用 Vagrant 和 Oracle VirtualBox 在 Ubuntu Virtual Machines 上设置了 Kubernetes 集群。我创建了 3 个节点集群,即 1 个主节点和 2 个工作节点。我可以成功连接到这些节点并且可以 运行 kubectl 命令。

我 运行 在主机 Mac OS 的笔记本电脑上安装这些虚拟机。现在,我想在我的 Mac 终端上访问同一个 Kubernetes 集群和 运行 kubectl 命令。

以下是我的 Vagrant 文件:-

# -*- 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 = "192.168.56."
MASTER_IP_START = 1
NODE_IP_START = 2
LB_IP_START = 30

# All Vagrant configuration is done below. The "2" 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("2") 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 = "base"
  config.vm.box = "ubuntu/bionic64"

  # 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 "public_network"
  #config.vm.network "private_network", ip: "55.55.55.5"
  #config.vm.network "private_network", type: "dhcp"
  #config.vm.network "public_network", :bridge => "en0: Wi-Fi (Wireless)", :ip => "192.168.56.2"
  #config.vm.network "public_network", :bridge => "en0: Wi-Fi (Wireless)", type: "dhcp"

  # 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 "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # 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 "kubemaster" do |node|
        # Name shown in the GUI
        node.vm.provider "virtualbox" do |vb|
            vb.name = "kubemaster"
            vb.memory = 2048
            vb.cpus = 2
        end
        node.vm.hostname = "kubemaster"
        node.vm.network :private_network, ip: IP_NW + "#{MASTER_IP_START + i}"
        node.vm.network "forwarded_port", guest: 22, host: "#{2710 + i}"

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

        node.vm.provision "setup-dns", type: "shell", :path => "ubuntu/update-dns.sh"

      end
  end


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

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

        node.vm.provision "setup-dns", type: "shell", :path => "ubuntu/update-dns.sh"
    end
  end
end

我的主机的 IP 地址是 192.168.1.5,而对于 Kubernetes,master、worker1 和 worker2 节点分别是 192.168.56.2、192.168.56.3 和 192.168.56.4。

我尝试了很多,但没有找到任何具体的解决方案。非常感谢您对此的建议。谢谢

我想你只是尝试使用 ssh 远程主服务器

使用 kubeconfig 文件是从集群外部与 kubernetes 集群交互的标准方式。所以这没有错。从安全的角度来看,在 kubeconfig 文件中使用管理员用户凭据不是一个好主意。为避免这种情况,您可以生成一个服务帐户令牌并在 kubeconfig 文件中使用它。使用适当的 RoleRoleBinding.

限制服务帐户的权限

检查此以了解如何使用服务帐户令牌创建 kubeconfig