Warning: file_get_contents(/data/phpspider/zhask/data//catemap/2/cmake/2.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Kubernetes kubectl未与minikube通信_Kubernetes_Kubectl_Minikube - Fatal编程技术网

Kubernetes kubectl未与minikube通信

Kubernetes kubectl未与minikube通信,kubernetes,kubectl,minikube,Kubernetes,Kubectl,Minikube,在当地与kubectl和minikube学习kubernetes。我可以通过kubectl看到这一点: > kubectl get all -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES pod/mongodb-deployment-8f6675bc5-tj

在当地与kubectl和minikube学习kubernetes。我可以通过kubectl看到这一点:

> kubectl get all -o wide

NAME                                     READY   STATUS    RESTARTS   AGE   IP           NODE       NOMINATED NODE   READINESS GATES
pod/mongodb-deployment-8f6675bc5-tjwsb   1/1     Running   0          20s   10.1.43.14   chris-x1   <none>           <none>
pod/mongo-express-78fcf796b8-9gbsd       1/1     Running   0          20s   10.1.43.15   chris-x1   <none>           <none>

NAME                            TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE   SELECTOR
service/kubernetes              ClusterIP      10.152.183.1     <none>        443/TCP          29m   <none>
service/mongo-express-service   LoadBalancer   10.152.183.254   <pending>     8081:30000/TCP   20s   app=mongo-express
service/mongodb-service         ClusterIP      10.152.183.115   <none>        27017/TCP        20s   app=mongodb

NAME                                 READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS      IMAGES          SELECTOR
deployment.apps/mongodb-deployment   1/1     1            1           20s   mongodb         mongo           app=mongodb
deployment.apps/mongo-express        1/1     1            1           21s   mongo-express   mongo-express   app=mongo-express

NAME                                           DESIRED   CURRENT   READY   AGE   CONTAINERS      IMAGES          SELECTOR
replicaset.apps/mongodb-deployment-8f6675bc5   1         1         1       20s   mongodb         mongo           app=mongodb,pod-template-hash=8f6675bc5
replicaset.apps/mongo-express-78fcf796b8       1         1         1       21s   mongo-express   mongo-express   app=mongo-express,pod-template-hash=78fcf796b8
>kubectl获得全宽
名称就绪状态重新启动老化IP节点指定节点就绪门
pod/mongodb-deployment-8f6675bc5-tjwsb 1/1运行0 20s 10.1.43.14 chris-x1
pod/mongo-express-78fcf796b8-9gbsd 1/1运行0 20秒10.1.43.15克里斯-x1
名称类型CLUSTER-IP外部IP端口年龄选择器
service/kubernetes ClusterIP 10.152.183.1 443/TCP 29m
service/mongo express service LoadBalancer 10.152.183.254 8081:30000/TCP 20s app=mongo express
服务/mongodb服务集群IP 10.152.183.115 27017/TCP 20s app=mongodb
名称就绪最新可用年龄容器图像选择器
deployment.apps/mongodb-deployment 1/120s mongodb mongo app=mongodb
deployment.apps/mongo-express 1/1 21s mongo express mongo express应用程序=mongo express
名称所需的当前就绪年龄容器图像选择器
replicaset.apps/mongodb-deployment-8f6675bc5 1 20s mongodb mongo app=mongodb,pod模板哈希=8f6675bc5
replicaset.apps/mongo-express-78fcf796b8 1 1 21s mongo express mongo express应用程序=mongo express,pod模板哈希=78fcf796b8
但当我在lanuch minikube仪表板上看到任何吊舱、部署、服务等。。。?就好像它们是从不同的集群中跑出来的。如果我将YAML配置直接粘贴到minikube仪表板中,那么我可以看到所有内容。真奇怪。。。为什么?

我可以使用minikube-kubectl命令,但这似乎不是它应该如何工作的


运行Ubuntu20、kubectl 1.20和minikube 1.17。

结果是我被设置为运行microk8s集群而不是minikube

chris@chris-x1 /v/w/p/k8s> kubectl config view

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: DATA+OMITTED
    server: https://127.0.0.1:16443
  name: microk8s-cluster
contexts:
- context:
    cluster: microk8s-cluster
    user: admin
  name: microk8s
current-context: microk8s
kind: Config
preferences: {}
users:
- name: admin
  user:
    token: REDACTED
因此,我需要按照以下步骤访问仪表板: