kubernetes - kubelet 没有配置 ClusterDNS IP，无法使用 "ClusterFirst"策略创建 Pod。回退到 DNSDefault 策略-6ren

kubernetes - kubelet 没有配置 ClusterDNS IP，无法使用 "ClusterFirst"策略创建 Pod。回退到 DNSDefault 策略

转载作者：行者123 更新时间：2023-12-01 13:31:19

刚开始使用 kubernetes。我有三台物理机:1 台主机，2 台节点。我做了基本的入门配置。一切似乎都在运行，节点可以与主节点通信，但是当我尝试安装示例应用程序时 ( see in following kubernetes guide )
我一遍又一遍地收到这个警告:

kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to DNSDefault policy.

我无法访问该应用程序:master_ip:30001

知道发生了什么以及如何解决它吗？

配置

这是配置:

$ kubectl get nodes

NAME                     STATUS    AGE       VERSION
master-precision-t1600   Ready     19h       v1.7.4
node2-precision-t1600    Ready     19h       v1.7.4

$ kubectl get pods --all-namespaces

NAMESPACE     NAME                                             READY     STATUS    RESTARTS   AGE
kube-system   etcd-master-precision-t1600                      1/1       Running   1          19h
kube-system   kube-apiserver-master-precision-t1600            1/1       Running   1          19h
kube-system   kube-controller-manager-master-precision-t1600   1/1       Running   1          19h
kube-system   kube-dns-2425271678-xrlp4                        3/3       Running   3          19h
kube-system   kube-proxy-58qm6                                 1/1       Running   1          19h
kube-system   kube-proxy-tjskl                                 1/1       Running   1          19h
kube-system   kube-scheduler-master-precision-t1600            1/1       Running   1          19h
kube-system   kubernetes-dashboard-3313488171-7n56j            1/1       Running   0          38m
kube-system   weave-net-1hjxl                                  2/2       Running   2          19h
kube-system   weave-net-lwk8r                                  2/2       Running   2          19h
sock-shop     carts-2469883122-h8f4n                           1/1       Running   0          1h
sock-shop     carts-db-1721187500-pkpk0                        1/1       Running   0          1h
sock-shop     catalogue-4293036822-hpkgp                       1/1       Running   0          1h
sock-shop     catalogue-db-1846494424-xlb8m                    1/1       Running   0          1h
sock-shop     front-end-2337481689-s8bkm                       1/1       Running   0          1h
sock-shop     orders-733484335-n7h4c                           1/1       Running   0          1h
sock-shop     orders-db-3728196820-12rt8                       1/1       Running   0          1h
sock-shop     payment-3050936124-kwqfs                         1/1       Running   0          1h
sock-shop     queue-master-2067646375-n8sgj                    1/1       Running   0          1h
sock-shop     rabbitmq-241640118-dqh6p                         1/1       Running   0          1h
sock-shop     shipping-2463450563-g01sw                        1/1       Running   0          1h
sock-shop     user-1574605338-kwqmp                            1/1       Running   0          1h
sock-shop     user-db-3152184577-w3f39                         1/1       Running   0          1h

$ kubectl describe nodes
Name:           master-precision-t1600
Role:           
Labels:         beta.kubernetes.io/arch=amd64
            beta.kubernetes.io/os=linux
            kubernetes.io/hostname=master-precision-t1600
            node-role.kubernetes.io/master=
Annotations:        node.alpha.kubernetes.io/ttl=0
            volumes.kubernetes.io/controller-managed-attach-detach=true
Taints:         node-role.kubernetes.io/master:NoSchedule
CreationTimestamp:  Tue, 22 Aug 2017 17:05:06 +0200
Conditions:
  Type          Status  LastHeartbeatTime           LastTransitionTime          Reason              Message
  ----          ------  -----------------           ------------------          ------              -------
  OutOfDisk         False   Wed, 23 Aug 2017 12:26:45 +0200     Tue, 22 Aug 2017 17:05:02 +0200     KubeletHasSufficientDisk    kubelet has sufficient disk space available
  MemoryPressure    False   Wed, 23 Aug 2017 12:26:45 +0200     Tue, 22 Aug 2017 17:05:02 +0200     KubeletHasSufficientMemory  kubelet has sufficient memory available
  DiskPressure      False   Wed, 23 Aug 2017 12:26:45 +0200     Tue, 22 Aug 2017 17:05:02 +0200     KubeletHasNoDiskPressure    kubelet has no disk pressure
  Ready         True    Wed, 23 Aug 2017 12:26:45 +0200     Tue, 22 Aug 2017 17:05:02 +0200     KubeletReady            kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:   xxx.xxx.xxx.215
  Hostname: master-precision-t1600
Capacity:
 alpha.kubernetes.io/nvidia-gpu:    0
 cpu:                   8
 memory:                8127968Ki
 pods:                  110
Allocatable:
 alpha.kubernetes.io/nvidia-gpu:    0
 cpu:                   8
 memory:                8025568Ki
 pods:                  110
System Info:
 Machine ID:            d718aa59fbe54581a9b058eb453ca453
 System UUID:           4C4C4544-005A-4410-805A-C4C04F32354A
 Boot ID:           687c603a-aad9-477a-a398-dfffeeaa4cd0
 Kernel Version:        4.10.0-32-generic
 OS Image:          Ubuntu 16.04.3 LTS
 Operating System:      linux
 Architecture:          amd64
 Container Runtime Version: docker://1.11.2
 Kubelet Version:       v1.7.4
 Kube-Proxy Version:        v1.7.4
ExternalID:         master-precision-t1600
Non-terminated Pods:        (8 in total)
  Namespace         Name                            CPU Requests    CPU Limits  Memory Requests Memory Limits
  ---------         ----                            ------------    ----------  --------------- -------------
  kube-system           etcd-master-precision-t1600             0 (0%)      0 (0%)      0 (0%)      0 (0%)
  kube-system           kube-apiserver-master-precision-t1600           250m (3%)   0 (0%)      0 (0%)      0 (0%)
  kube-system           kube-controller-manager-master-precision-t1600      200m (2%)   0 (0%)      0 (0%)      0 (0%)
  kube-system           kube-dns-2425271678-xrlp4               260m (3%)   0 (0%)      110Mi (1%)  170Mi (2%)
  kube-system           kube-proxy-58qm6                    0 (0%)      0 (0%)      0 (0%)      0 (0%)
  kube-system           kube-scheduler-master-precision-t1600           100m (1%)   0 (0%)      0 (0%)      0 (0%)
  kube-system           kubernetes-dashboard-3313488171-7n56j           0 (0%)      0 (0%)      0 (0%)      0 (0%)
  kube-system           weave-net-1hjxl                     20m (0%)    0 (0%)      0 (0%)      0 (0%)
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  CPU Requests  CPU Limits  Memory Requests Memory Limits
  ------------  ----------  --------------- -------------
  830m (10%)    0 (0%)      110Mi (1%)  170Mi (2%)
Events:
  FirstSeen LastSeen    Count   From                SubObjectPath   Type        Reason          Message
  --------- --------    -----   ----                -------------   --------    ------          -------
  39m       30s     36  kubelet, master-precision-t1600         Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "kubernetes-dashboard-3313488171-7n56j_kube-system(1ed597d4-87e8-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.


Name:           node2-precision-t1600
Role:           
Labels:         beta.kubernetes.io/arch=amd64
            beta.kubernetes.io/os=linux
            kubernetes.io/hostname=node2-precision-t1600
Annotations:        node.alpha.kubernetes.io/ttl=0
            volumes.kubernetes.io/controller-managed-attach-detach=true
Taints:         <none>
CreationTimestamp:  Tue, 22 Aug 2017 17:10:43 +0200
Conditions:
  Type          Status  LastHeartbeatTime           LastTransitionTime          Reason              Message
  ----          ------  -----------------           ------------------          ------              -------
  OutOfDisk         False   Wed, 23 Aug 2017 12:26:49 +0200     Wed, 23 Aug 2017 11:42:43 +0200     KubeletHasSufficientDisk    kubelet has sufficient disk space available
  MemoryPressure    False   Wed, 23 Aug 2017 12:26:49 +0200     Wed, 23 Aug 2017 11:42:43 +0200     KubeletHasSufficientMemory  kubelet has sufficient memory available
  DiskPressure      False   Wed, 23 Aug 2017 12:26:49 +0200     Wed, 23 Aug 2017 11:42:43 +0200     KubeletHasNoDiskPressure    kubelet has no disk pressure
  Ready         True    Wed, 23 Aug 2017 12:26:49 +0200     Wed, 23 Aug 2017 11:42:43 +0200     KubeletReady            kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:   129.241.110.167
  Hostname: node2-precision-t1600
Capacity:
 alpha.kubernetes.io/nvidia-gpu:    1
 cpu:                   8
 memory:                8127968Ki
 pods:                  110
Allocatable:
 alpha.kubernetes.io/nvidia-gpu:    1
 cpu:                   8
 memory:                8025568Ki
 pods:                  110
System Info:
 Machine ID:            d701c70173f547168978ca276552bb88
 System UUID:           4C4C4544-005A-4410-805A-B5C04F32354A
 Boot ID:           827de455-66cb-481d-a362-557a17db11f4
 Kernel Version:        4.10.0-32-generic
 OS Image:          Ubuntu 16.04.3 LTS
 Operating System:      linux
 Architecture:          amd64
 Container Runtime Version: docker://1.11.2
 Kubelet Version:       v1.7.4
 Kube-Proxy Version:        v1.7.4
ExternalID:         node2-precision-t1600
Non-terminated Pods:        (15 in total)
  Namespace         Name                    CPU Requests    CPU Limits  Memory Requests Memory Limits
  ---------         ----                    ------------    ----------  --------------- -------------
  kube-system           kube-proxy-tjskl            0 (0%)      0 (0%)      0 (0%)      0 (0%)
  kube-system           weave-net-lwk8r             20m (0%)    0 (0%)      0 (0%)      0 (0%)
  sock-shop         carts-2469883122-h8f4n          0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         carts-db-1721187500-pkpk0       0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         catalogue-4293036822-hpkgp      0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         catalogue-db-1846494424-xlb8m       0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         front-end-2337481689-s8bkm      100m (1%)   0 (0%)      100Mi (1%)  0 (0%)
  sock-shop         orders-733484335-n7h4c          0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         orders-db-3728196820-12rt8      0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         payment-3050936124-kwqfs        0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         queue-master-2067646375-n8sgj       0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         rabbitmq-241640118-dqh6p        0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         shipping-2463450563-g01sw       0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         user-1574605338-kwqmp           0 (0%)      0 (0%)      0 (0%)      0 (0%)
  sock-shop         user-db-3152184577-w3f39        0 (0%)      0 (0%)      0 (0%)      0 (0%)
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  CPU Requests  CPU Limits  Memory Requests Memory Limits
  ------------  ----------  --------------- -------------
  120m (1%) 0 (0%)      100Mi (1%)  0 (0%)
Events:
  FirstSeen LastSeen    Count   From                    SubObjectPath   Type        Reason          Message
  --------- --------    -----   ----                    -------------   --------    ------          -------
  44m       44m     1   kubelet, node2-precision-t1600              Normal      NodeReady       Node node2-precision-t1600 status is now: NodeReady
  44m       44m     3   kubelet, node2-precision-t1600              Normal      NodeHasSufficientDisk   Node node2-precision-t1600 status is now: NodeHasSufficientDisk
  44m       44m     3   kubelet, node2-precision-t1600              Normal      NodeHasSufficientMemory Node node2-precision-t1600 status is now: NodeHasSufficientMemory
  44m       44m     3   kubelet, node2-precision-t1600              Normal      NodeHasNoDiskPressure   Node node2-precision-t1600 status is now: NodeHasNoDiskPressure
  44m       44m     1   kubelet, node2-precision-t1600              Normal      NodeAllocatableEnforced Updated Node Allocatable limit across pods
  44m       44m     1   kubelet, node2-precision-t1600              Warning     Rebooted        Node node2-precision-t1600 has been rebooted, boot id: 827de455-66cb-481d-a362-557a17db11f4
  44m       44m     1   kubelet, node2-precision-t1600              Normal      Starting        Starting kubelet.
  44m       44m     1   kube-proxy, node2-precision-t1600           Normal      Starting        Starting kube-proxy.
  43m       11m     9   kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "rabbitmq-241640118-dqh6p_sock-shop(79e3bb08-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  44m       5m      24  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "orders-db-3728196820-12rt8_sock-shop(79ca1e21-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  44m       2m      22  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "payment-3050936124-kwqfs_sock-shop(79cb96f4-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  44m       2m      28  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "shipping-2463450563-g01sw_sock-shop(79fa9dd4-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  43m       2m      22  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "carts-2469883122-h8f4n_sock-shop(79bbf964-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  44m       1m      30  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "user-db-3152184577-w3f39_sock-shop(7a303582-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  44m       1m      16  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "user-1574605338-kwqmp_sock-shop(7a11a937-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  44m       1m      20  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "catalogue-db-1846494424-xlb8m_sock-shop(79c24789-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  44m       54s     26  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "queue-master-2067646375-n8sgj_sock-shop(79d46bb2-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  44m       45s     30  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "front-end-2337481689-s8bkm_sock-shop(79c49a6c-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  44m       24s     11  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "carts-db-1721187500-pkpk0_sock-shop(79bd1f99-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  43m       11s     25  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "catalogue-4293036822-hpkgp_sock-shop(79bf628c-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  43m       3s      25  kubelet, node2-precision-t1600              Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "orders-733484335-n7h4c_sock-shop(79c6f31c-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.
  43m       0s      228 kubelet, node2-precision-t1600              Warning     MissingClusterDNS   (combined from similar events): kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "payment-3050936124-kwqfs_sock-shop(79cb96f4-87e4-11e7-ab01-782bcba630bb)". Falling back to DNSDefault policy.

编辑1:

正如迈克在他的回答中告诉我的那样，我通过以下方式获得了 DNS IP: kubectl get services --namespace=kube-system .到目前为止，我尝试更改命令行标志的方法:

在 ExecStart kubeadm.conf 中添加 --cluster-dns 10.96.0.10

执行 kubelet --cluster-dns 10.96.0.10

都没有结果

最佳答案

kubelet 服务需要一个命令行标志来设置集群 DNS IP - 看起来您正在运行 kube-dns，因此您可以通过运行 kubectl get services --namespace=kube-system 来获取该 IP。或者从 kube-dns 服务 YAML 或 JSON 配置的“ClusterIP”字段中获取 IP。

获得 IP 后，您必须设置 --cluster-dns kubelet 的命令行标志。

我没有使用 kubeadm 来设置集群，所以我不确定它是如何运行服务的，也不能说如何更改命令行标志 - 希望知道的人可以提供该部分的输入。

关于kubernetes - kubelet 没有配置 ClusterDNS IP，无法使用 "ClusterFirst"策略创建 Pod。回退到 DNSDefault 策略，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/45837246/

文章推荐： java - 警报 JSP 后保持输入的详细信息不变

文章推荐： java - 设置ejb定时器任务的参数来执行后端进程

文章推荐： java - Xades4j验证封装签名

文章推荐： Angular 4 订阅 paramMap 不适用于 child socket

kubelet - Microk8s 在哪里保存 kubelet.service？
我正在尝试 enable a FlexVolume driver在 Ubuntu 上的 Microk8s 上。为此，我似乎必须编辑 kubelet.service 文件。这应该存储在/etc/sys
kubernetes - kubelet 无法获取 docker 和 kubelet 服务的 cgroup 统计信息
我正在裸机 Debian 上运行 kubernetes(目前有 3 个 master、2 个worker、PoC)。我按照 k8s-the-hard-way 进行操作，但在 kubelet 上遇到了以
linux - kubelet 失败，kubelet cgroup 驱动程序 : "cgroupfs" is different from docker cgroup driver: "systemd"
cgroup driver的配置在/etc/systemd/system/kubelet.service.d/10-kubeadm.conf Environment="KUBELET_CGROUP_A
docker - kubernetes 1.12.2 加载 Kubelet 配置文件/var/lib/kubelet/config.yaml 失败
环境: Kubernetes 1.12.2 Docker 18.9.0 microk8s.kubectl $ k 得到所有 NAME
kubelet 配置资源预留的姿势
Kubernetes 的节点可以按照节点的资源容量进行调度，默认情况下 Pod 能够使用节点全部可用容量。这样就会造成一个问题，因为节点自己通常运行了不少驱动 OS 和 Kubernetes 的
kubernetes - kubelet 服务未启动
在运行 kubectl get nodes 等命令时出现以下错误: 与服务器 :6443 的连接被拒绝 - 您是否指定了正确的主机或端口？我运行了 systemctl status kubelet.
centos - Kubelet 启动尝试失败会污染日志
我在 AWS 上安装了一堆新的 CentOS 服务器。服务 kubelet 尝试启动会污染日志文件(var/log/messages)，但由于我没有用它，我想将其删除。这是 CentOS 的一个可选组
docker - Kubelet 错误地认为磁盘已满
我在 kubelet 删除 docker 图像时遇到问题，因为它认为磁盘已满: Dec 29 18:00:14 hostname kubelet: I1229 18:00:14.548513 13
docker - kubelet-Docker容器通信如何发生？
我想知道kubelet如何与docker容器通信。此配置在哪里定义？我进行了很多搜索，但没有发现任何有用的信息。我正在使用https kube API服务器。我可以创建 pods ，但不会产生容器吗？
kubernetes - kubelet 动态配置不起作用
https://kubernetes.io/docs/tasks/administer-cluster/reconfigure-kubelet/嗨，我在学习本教程时遇到了一些麻烦。建议使用 confi
kubernetes - Kubelet 停止发布节点状态
我的两个集群节点获得 Kubelet stopped posting node status在 kubectl describe node有时。在该节点的日志中，我看到了这一点: Dec 11 12:
kubernetes - Kubelet 配置
我在某些 kubernetes 节点上的 CentO 上遇到了 OOM 问题。我想像他们在演示中那样设置它: --kube-reserved is set to cpu=1,memory=2Gi,ep
浅析 Kubelet 驱逐机制
Kubelet 出于对节点的保护，允许在节点资源不足的情况下，开启对节点上 Pod 进行驱逐的功能。最近对 Kubelet 的驱逐机制有所研究，发现其中有很多值得学习的地方，总结下来
kubernetes - 重启 kubelet 会停止所有节点吗？
如果我运行 systemctl restart kubelet它会影响其他正在运行的节点吗？它会停止集群吗？你能预见任何影响吗？任何帮助，将不胜感激! 最佳答案在回答之前，小声明:重启不是由于对
kubernetes - 运行 kubelet 时出错
我正在尝试在 fedora 24/lxc 容器上启动 kubelet，但收到一个似乎与 libvirt/iptables 相关的错误 Docker(使用 dnf/yum 安装): [root@node
kubernetes - kubelet 说找不到节点 "master01"
我尝试使用堆叠我的 kubeadm 集群三大师。我从我的 init 命令收到这个问题... [kubelet-check] Initial timeout of 40s passed. Unfor
kubernetes - Kubernetes kubelet 日志位于何处？
我在我的 Ubuntu 机器上安装了 Kubernetes。出于某些调试目的，我需要查看 kubelet 日志文件(如果有任何此类文件)。我看过 /var/logs但我找不到这样的文件。那可能在哪里
kubernetes - 容器化 kubelet 和本地磁盘卷生命周期
平台:OEL 7.7 + kube 1.15.5 + docker 19.03.1 我们正在使用容器化 kubelet 方法在 k8s 上构建一个纠删码对象存储。我们很难提出可行的磁盘生命周期方法。就
deployment - kubelet 在初始部署后未注册，但需要重新启动
我有一个来自 kubelet 的奇怪行为，在集群启动后不久 kubelet 没有注册到 API 服务器。有趣的是，如果我重新启动 kubelet 守护程序，它会正确注册并且一切都按预期工作，这让我相
kubernetes - Kubernetes集群: “” kubelet.service的依赖项作业失败“”
我只想知道你们中的任何人以前是否曾经听过本教程并获得成功。我不知道为什么，但是每当我在MINION端重新启动并启用服务时，它总是失败，并显示错误“kubelet.service的依赖项作业失败”，当

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

kubernetes - kubelet 没有配置 ClusterDNS IP，无法使用 "ClusterFirst"策略创建 Pod。回退到 DNSDefault 策略