Kubernetes 如何在本地集群中获取minikube节点
我正在尝试使用VM和minikube设置本地群集,因为我一直在读取它只能用于本地目的,但我想加入一台辅助计算机,我正在寻找一种方法来创建联接和哈希。这在minikube中是不可能的。使用minikube,操作域是一台笔记本电脑或本地机器。你不能加入一个额外的节点,你需要使用类似的东西来构建一个完整的集群。如果你的minikube机器正在使用VirtualBox,你可以很容易地做到这一点Kubernetes 如何在本地集群中获取minikube节点,kubernetes,minikube,Kubernetes,Minikube,我正在尝试使用VM和minikube设置本地群集,因为我一直在读取它只能用于本地目的,但我想加入一台辅助计算机,我正在寻找一种方法来创建联接和哈希。这在minikube中是不可能的。使用minikube,操作域是一台笔记本电脑或本地机器。你不能加入一个额外的节点,你需要使用类似的东西来构建一个完整的集群。如果你的minikube机器正在使用VirtualBox,你可以很容易地做到这一点 启动minikube: $ minikube start --vm-driver="virtualbox"
$ minikube start --vm-driver="virtualbox"
$ kubectl version
$ minikube ssh
$ kubelet --version
$ kubeadm token create --print-join-command
$ curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
$ cat <<EOF >/etc/apt/sources.list.d/kubernetes.list
deb http://apt.kubernetes.io/ kubernetes-xenial main
EOF
$ apt-get update
$ kubeadm join 192.168.xx.yy:8443 --token asdfasf.laskjflakflsfla --discovery-token-ca-cert-hash sha256:shfkjshkfjhskjfskjdfhksfh...shdfk
$ kubectl apply -f https://docs.projectcalico.org/v3.0/getting-started/kubernetes/installation/hosted/kubeadm/1.7/calico.yaml
$ kubectl get nodes:
NAME STATUS ROLES AGE VERSION
minikube Ready master 1h v1.10.0
ubuntu-xenial Ready <none> 36m v1.10.0
$ kubectl get pods --all-namespaces -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE
kube-system calico-etcd-982l8 1/1 Running 0 10m 10.0.2.15 minikube
kube-system calico-kube-controllers-79dccdc4cc-66zxm 1/1 Running 0 10m 10.0.2.15 minikube
kube-system calico-node-9sgt5 1/2 Running 13 10m 10.0.2.15 ubuntu-xenial
kube-system calico-node-qtpg2 2/2 Running 0 10m 10.0.2.15 minikube
kube-system etcd-minikube 1/1 Running 0 1h 10.0.2.15 minikube
kube-system heapster-6hmhs 1/1 Running 0 1h 172.17.0.4 minikube
kube-system influxdb-grafana-69s5s 2/2 Running 0 1h 172.17.0.5 minikube
kube-system kube-addon-manager-minikube 1/1 Running 0 1h 10.0.2.15 minikube
kube-system kube-apiserver-minikube 1/1 Running 0 1h 10.0.2.15 minikube
kube-system kube-controller-manager-minikube 1/1 Running 0 1h 10.0.2.15 minikube
kube-system kube-dns-86f4d74b45-tzc4r 3/3 Running 0 1h 172.17.0.2 minikube
kube-system kube-proxy-vl5mq 1/1 Running 0 1h 10.0.2.15 minikube
kube-system kube-proxy-xhv8s 1/1 Running 2 35m 10.0.2.15 ubuntu-xenial
kube-system kube-scheduler-minikube 1/1 Running 0 1h 10.0.2.15 minikube
kube-system kubernetes-dashboard-5498ccf677-7gf4j 1/1 Running 0 1h 172.17.0.3 minikube
kube-system storage-provisioner 1/1 Running 0 1h 10.0.2.15 minikube
$kubectl获取节点:
姓名状态角色年龄版本
minikube Ready master 1h v1.10.0
ubuntu xenial Ready 36m v1.10.0
$kubectl获得吊舱--所有名称空间-o宽
命名空间名称就绪状态重新启动旧IP节点
kube系统calico-etcd-982l8 1/1运行0 10m 10.0.2.15迷你kube
kube系统calico-kube-controllers-79dccdc4cc-66zxm 1/1运行0 10m 10.0.2.15 minikube
kube系统calico-node-9sgt5 1/2运行13 10m 10.0.2.15 ubuntu xenial
kube系统印花布节点-qtpg2 2/2运行0 10m 10.0.2.15迷你kube
kube系统etcd minikube 1/1运行0 1h 10.0.2.15 minikube
kube系统heapster-6hmhs 1/1运行0 1h 172.17.0.4迷你kube
kube系统XDB-grafana-69s5s 2/2运行0 1h 172.17.0.5迷你kube
kube系统kube插件管理器minikube 1/1运行0 1h 10.0.2.15 minikube
kube系统kube apiserver minikube 1/1运行0 1h 10.0.2.15 minikube
kube系统kube控制器管理器minikube 1/1运行0 1h 10.0.2.15 minikube
kube系统kube-dns-86f4d74b45-tzc4r 3/3运行0 1h 172.17.0.2迷你kube
kube系统kube-proxy-vl5mq 1/1运行0 1h 10.0.2.15迷你kube
kube系统kube-proxy-xhv8s 1/1运行2 35m 10.0.2.15 ubuntu xenial
kube系统kube调度程序minikube 1/1运行0 1h 10.0.2.15 minikube
kube系统kubernetes-dashboard-5498ccf677-7gf4j 1/1运行0 1h 172.17.0.3迷你kube
运行0 1h 10.0.2.15 minikube的kube系统存储供应器1/1
请分享流浪汉文件为什么是“网络解决方案”“有必要吗?它有什么作用?我担心它只适用于K8S1.7。如果多节点需要,为什么不内置在k8s中?我阅读了yaml文件,它是一个守护程序、etcd、一堆POD和一个服务。需要网络解决方案来与不同节点上的POD通信。最新版本的k8s仍然需要它。它不是k8s内置的,因为存在多个网络插件。由您决定要使用哪个插件。192.168.0.0/16子网是calico插件的默认子网。如果你想使用flannel,你需要在将它应用到集群之前调整它的yaml文件。
$ kubectl get nodes:
NAME STATUS ROLES AGE VERSION
minikube Ready master 1h v1.10.0
ubuntu-xenial Ready <none> 36m v1.10.0
$ kubectl get pods --all-namespaces -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE
kube-system calico-etcd-982l8 1/1 Running 0 10m 10.0.2.15 minikube
kube-system calico-kube-controllers-79dccdc4cc-66zxm 1/1 Running 0 10m 10.0.2.15 minikube
kube-system calico-node-9sgt5 1/2 Running 13 10m 10.0.2.15 ubuntu-xenial
kube-system calico-node-qtpg2 2/2 Running 0 10m 10.0.2.15 minikube
kube-system etcd-minikube 1/1 Running 0 1h 10.0.2.15 minikube
kube-system heapster-6hmhs 1/1 Running 0 1h 172.17.0.4 minikube
kube-system influxdb-grafana-69s5s 2/2 Running 0 1h 172.17.0.5 minikube
kube-system kube-addon-manager-minikube 1/1 Running 0 1h 10.0.2.15 minikube
kube-system kube-apiserver-minikube 1/1 Running 0 1h 10.0.2.15 minikube
kube-system kube-controller-manager-minikube 1/1 Running 0 1h 10.0.2.15 minikube
kube-system kube-dns-86f4d74b45-tzc4r 3/3 Running 0 1h 172.17.0.2 minikube
kube-system kube-proxy-vl5mq 1/1 Running 0 1h 10.0.2.15 minikube
kube-system kube-proxy-xhv8s 1/1 Running 2 35m 10.0.2.15 ubuntu-xenial
kube-system kube-scheduler-minikube 1/1 Running 0 1h 10.0.2.15 minikube
kube-system kubernetes-dashboard-5498ccf677-7gf4j 1/1 Running 0 1h 172.17.0.3 minikube
kube-system storage-provisioner 1/1 Running 0 1h 10.0.2.15 minikube