k8s中flannel:镜像下载不了
重新部署一套K8S集群时，由于K8S需要扁平化的网络，所以当执行下面的
- root@master ~]# kubectl apply -f kube-flannel.yml
会开始下载镜像，然后去启动，结果等了几分钟，一直没有好
- [root@k8s-master ~]# kubectl get pod -n kube-system
- NAME READY STATUS RESTARTS AGE
- coredns-58cc8c89f4-9gn5g 0/1 Pending 0 27m
- coredns-58cc8c89f4-xxzx7 0/1 Pending 0 27m
- etcd-k8s-master 1/1 Running 1 26m
- kube-apiserver-k8s-master 1/1 Running 1 26m
- kube-controller-manager-k8s-master 1/1 Running 1 26m
- kube-flannel-ds-amd64-2dqlf 0/1 Init:ImagePullBackOff 0 11m
- kube-proxy-rn98b 1/1 Running 1 27m
- kube-scheduler-k8s-master 1/1 Running 1 26m
- [root@k8s-master ~]# kubectl get pod -n kube-system
去查询pod
- [root@k8s-master ~]# kubectl describe pod kube-flannel-ds-amd64-2dqlf -n kube-system
- Name: kube-flannel-ds-amd64-2dqlf
- Namespace: kube-system
- Priority: 0
- Node: k8s-master/192.168.180.130
- Start Time: Thu, 19 Dec 2019 22:36:13 +0800
- Labels: app=flannel
- controller-revision-hash=67f65bfbc7
- pod-template-generation=1
- tier=node
- Annotations: <none>
- Status: Pending
- IP: 192.168.180.130
- IPs:
- IP: 192.168.180.130
- Controlled By: DaemonSet/kube-flannel-ds-amd64
- Init Containers:
- install-cni:
- Container ID:
- Image: quay.io/coreos/flannel:v0.11.0-amd64
- Image ID:
- Port: <none>
- Host Port: <none>
- Command:
- cp
- Args:
- -f
- /etc/kube-flannel/cni-conf.json
- /etc/cni/net.d/10-flannel.conflist
- State: Waiting
- Reason: ImagePullBackOff
- Ready: False
- Restart Count: 0
- Environment: <none>
- Mounts:
- /etc/cni/net.d from cni (rw)
- /etc/kube-flannel/ from flannel-cfg (rw)
- /var/run/secrets/kubernetes.io/serviceaccount from flannel-token-r52cd (ro)
- Containers:
- kube-flannel:
- Container ID:
- Image: quay.io/coreos/flannel:v0.11.0-amd64
- Image ID:
- Port: <none>
- Host Port: <none>
- Command:
- /opt/bin/flanneld
- Args:
- --ip-masq
- --kube-subnet-mgr
- State: Waiting
- Reason: PodInitializing
- Ready: False
- Restart Count: 0
- Limits:
- cpu: 100m
- memory: 50Mi
- Requests:
- cpu: 100m
- memory: 50Mi
- Environment:
- POD_NAME: kube-flannel-ds-amd64-2dqlf (v1:metadata.name)
- POD_NAMESPACE: kube-system (v1:metadata.namespace)
- Mounts:
- /etc/kube-flannel/ from flannel-cfg (rw)
- /run/flannel from run (rw)
- /var/run/secrets/kubernetes.io/serviceaccount from flannel-token-r52cd (ro)
- Conditions:
- Type Status
- Initialized False
- Ready False
- ContainersReady False
- PodScheduled True
- Volumes:
- run:
- Type: HostPath (bare host directory volume)
- Path: /run/flannel
- HostPathType:
- cni:
- Type: HostPath (bare host directory volume)
- Path: /etc/cni/net.d
- HostPathType:
- flannel-cfg:
- Type: ConfigMap (a volume populated by a ConfigMap)
- Name: kube-flannel-cfg
- Optional: false
- flannel-token-r52cd:
- Type: Secret (a volume populated by a Secret)
- SecretName: flannel-token-r52cd
- Optional: false
- QoS Class: Burstable
- Node-Selectors: <none>
- Tolerations: :NoSchedule
- node.kubernetes.io/disk-pressure:NoSchedule
- node.kubernetes.io/memory-pressure:NoSchedule
- node.kubernetes.io/network-unavailable:NoSchedule
- node.kubernetes.io/not-ready:NoExecute
- node.kubernetes.io/pid-pressure:NoSchedule
- node.kubernetes.io/unreachable:NoExecute
- node.kubernetes.io/unschedulable:NoSchedule
- Events:
- Type Reason Age From Message
- ---- ------ ---- ---- -------
- Normal Scheduled <unknown> default-scheduler Successfully assigned kube-system/kube-flannel-ds-amd64-2dqlf to k8s-master
- Warning Failed 5m29s kubelet, k8s-master Failed to pull image "quay.io/coreos/flannel:v0.11.0-amd64": rpc error: code = Unknown desc = context canceled
- Warning Failed 4m21s (x2 over 5m2s) kubelet, k8s-master Failed to pull image "quay.io/coreos/flannel:v0.11.0-amd64": rpc error: code = Unknown desc = Error response from daemon: Get https://quay.io/v2/: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
- Normal Pulling 3m31s (x4 over 7m5s) kubelet, k8s-master Pulling image "quay.io/coreos/flannel:v0.11.0-amd64"
- Warning Failed 3m18s (x4 over 5m29s) kubelet, k8s-master Error: ErrImagePull
- Warning Failed 3m18s kubelet, k8s-master Failed to pull image "quay.io/coreos/flannel:v0.11.0-amd64": rpc error: code = Unknown desc = Error response from daemon: Get https://quay.io/v2/coreos/flannel/manifests/v0.11.0-amd64: Get https://quay.io/v2/auth?scope=repository%3Acoreos%2Fflannel%3Apull&service=quay.io: net/http: TLS handshake timeout
- Normal BackOff 3m5s (x6 over 5m29s) kubelet, k8s-master Back-off pulling image "quay.io/coreos/flannel:v0.11.0-amd64"
- Warning Failed 2m2s (x11 over 5m29s) kubelet, k8s-master Error: ImagePullBackOff
发现时镜像拉取失败的原因，有可能时网络原因导致的，之前都没有遇到过
- kube-flannel-ds-amd64-2dqlf 0/1 Init:ImagePullBackOff 0 11m
这个状态，应该时yaml中，有一个InitC，初始化的容器，便去查看一番
所以只能把别的集群中的镜像导出一份，在导入
- [root@k8s-master mnt]# docker load -i flannel.tar
- 7bff100f35cb: Loading layer [==================================================>] 4.672MB/4.672MB
- 5d3f68f6da8f: Loading layer [==================================================>] 9.526MB/9.526MB
- 9b48060f404d: Loading layer [==================================================>] 5.912MB/5.912MB
- 3f3a4ce2b719: Loading layer [==================================================>] 35.25MB/35.25MB
- 9ce0bb155166: Loading layer [==================================================>] 5.12kB/5.12kB
- Loaded image: quay.io/coreos/flannel:v0.11.0-amd64
- [root@k8s-master mnt]# docker images
- REPOSITORY TAG IMAGE ID CREATED SIZE
- registry.aliyuncs.com/google_containers/kube-apiserver v1.16.0 b305571ca60a 3 months ago 217MB
- registry.aliyuncs.com/google_containers/kube-proxy v1.16.0 c21b0c7400f9 3 months ago 86.1MB
- registry.aliyuncs.com/google_containers/kube-controller-manager v1.16.0 06a629a7e51c 3 months ago 163MB
- registry.aliyuncs.com/google_containers/kube-scheduler v1.16.0 301ddc62b80b 3 months ago 87.3MB
- registry.aliyuncs.com/google_containers/etcd 3.3.15-0 b2756210eeab 3 months ago 247MB
- registry.aliyuncs.com/google_containers/coredns 1.6.2 bf261d157914 4 months ago 44.1MB
- quay.io/coreos/flannel v0.11.0-amd64 ff281650a721 10 months ago 52.6MB
- registry.aliyuncs.com/google_containers/pause 3.1 da86e6ba6ca1 24 months ago 742kB
- [root@k8s-master mnt]# cd
- [root@k8s-master ~]# kubectl get node
- NAME STATUS ROLES AGE VERSION
- k8s-master Ready master 54m v1.16.1
- k8s-node01 NotReady <none> 15m v1.16.1
- k8s-node02 Ready <none> 17m v1.16.1
- [root@k8s-master ~]# kubectl get pod -n kube-system
- NAME READY STATUS RESTARTS AGE
- coredns-58cc8c89f4-9gn5g 1/1 Running 0 54m
- coredns-58cc8c89f4-xxzx7 1/1 Running 0 54m
- etcd-k8s-master 1/1 Running 1 53m
- kube-apiserver-k8s-master 1/1 Running 1 53m
- kube-controller-manager-k8s-master 1/1 Running 2 53m
- kube-flannel-ds-amd64-4bc88 1/1 Running 0 17m
- kube-flannel-ds-amd64-lzwd6 1/1 Running 0 19m
- kube-flannel-ds-amd64-vw4vn 1/1 Running 0 15m
- kube-proxy-bs8sd 1/1 Running 1 15m
- kube-proxy-nfvtt 1/1 Running 0 17m
- kube-proxy-rn98b 1/1 Running 1 54m
- kube-scheduler-k8s-master 1/1 Running 1 53m
- [root@k8s-master ~]# kubectl get node
- NAME STATUS ROLES AGE VERSION
- k8s-master Ready master 54m v1.16.1
- k8s-node01 Ready <none> 15m v1.16.1
- k8s-node02 Ready <none> 17m v1.16.1
稍等一会，就可以了。由于百度云连接经常失效，有需要镜像的，可以和我联系
k8s中flannel:镜像下载不了的更多相关文章
- 使用kubeadm安装kubernetes/部署前准备/flannel网络插件/镜像下载/
本文内容参考<kuberneters进阶实战>/马哥的新书/推荐 部署前的准备 主机名称解析 分布式系统环境中的多主机通信通常基于主机名称进行,这在IP地址存在变化的可能性时为主机提供了固 ...
- [转帖]k8s.gcr.io镜像无法下载的问题
k8s.gcr.io镜像无法下载的问题 https://blog.51cto.com/liuzhengwei521/2301497 看了下 赵安家老师应该是青岛人 在济南顺能网络科技有限公司上班 铭盛 ...
- k8s.gcr.io、gcr.io仓库的镜像下载
镜像下载.域名解析.时间同步请点击 阿里巴巴开源镜像站 获取这类镜像的方法一般有2种: 1.通过拉取国内镜像仓库的内容(操作简单直接拉取即可,缺点是镜像的版本更新可能较慢,可能无法获取最新的镜像) 2 ...
- 新版的K8S中的flannel.yaml文件中要注意的细节
部署flannel作为k8s中的网络插件,yaml文件都大小同异. 但在要注意以下细节. 以前,只需要前面master判断. 现在也需要有not-ready状态了. tolerations: - ke ...
- 转 docker创建私有仓库和k8s中使用私有镜像
docker私有仓库建立 环境说明我们选取192.168.5.2做私有仓库地址yum install docker -y1.启动docker仓库端口服务 docker run -d -p 5000:5 ...
- 【解决】k8s 1.15.2 镜像下载方案
k8s 国内镜像下载方案 众所周知,国内是不太容易下载k8s.gcr.io站点的镜像的 一.第一种方案:Azure中国镜像站 http://mirror.azure.cn/help/gcr-proxy ...
- 如何在K8S中优雅的使用私有镜像库 (Docker版)
前言 在企业落地 K8S 的过程中,私有镜像库 (专用镜像库) 必不可少,特别是在 Docker Hub 开始对免费用户限流之后, 越发的体现了搭建私有镜像库的重要性. 私有镜像库不但可以加速镜像的拉 ...
- eclipse javaEE版下载过程中选择镜像（Select Another Mirror）无反应解决办法，附带eclipse javaEE版下载教程。
1.eclipse javaEE版下载过程中选择镜像(Select Another Mirror)无反应 (复制该网址下载即可 https://mirrors.neusoft.edu.cn/eclip ...
- 入门 - k8s滚动更新部署中的镜像版本 （七）
目标 使用 kubectl 执行 Rolling Update(滚动更新) 更新应用程序 用户期望应用程序始终可用,为此开发者/运维者在更新应用程序时要分多次完成.在 Kubernetes 中,这是通 ...
随机推荐
- 自然语言处理工具hanlp定制用户词条
作者:baiziyu 关于hanlp的文章已经分享过很多,似乎好像大部分以理论性的居多.最近有在整理一些hanlp应用项目中的文章,待整理完成后会陆续分享出来.本篇分享的依然是由baiziyu 分享的 ...
- CentOS 7 配置 kcptun 实现网站加速
目的:shadowsocks+kcptun 实现vpn加速(shadowsocks,kcptun在同一台VPS上) 一.shadowsocks安装(参考 https://www.cnblogs.co ...
- python-day31(正式学习)
一.单机架构 应用领域: 植物大战僵尸 office 二.CS架构 应用领域: QQ 大型网络游戏 计算机发展初期用户去取数据,直接就去主机拿,从这里开始就分出了客户端和服务端. 客户端:用户安装的软 ...
- Linux 测试IP和端口是否能访问
一. 使用wget判断 wget是linux下的下载工具,需要先安装. 用法: wget ip:port 连接存在的端口 转自:https://blog.csdn.net/weixin_3768923 ...
- ftp服务器上传下载共享文件
1 windows下搭建ftp服务器 https://blog.csdn.net/qq_34610293/article/details/79210539 搭建好之后浏览器输入 ftp://ip就可以 ...
- Angular获取dom元素，以及父子组建之间相互传值
1.使用原生js代码获取dom元素 在ts文件中有一个ngOnInit()的方法,这个方式是指在模块加载完毕之后并不是dom加载完毕,也就是说如果你的dom元素中使用的angular的指令,然后想在这 ...
- [转载]for、foreach、iterator的用法及效率区别
来源:https://www.jianshu.com/p/bbb220824c9a 1.在形式上 for的形式是 for(int i=0;i<arr.size();i++){...} forea ...
- 线程的函数中调用MFC对话框类的变量
线程的函数中调用MFC对话框类的变量多线程传输文件的对话框 现在想要在对话框上添加一个进度条 为进度条映射变量m_progress这就需要在传输一段文件后就更新m_progress的值使进度条前进 也 ...
- linux下/etc/rc.d目录的介绍及redhat启动顺序
init inittab rc0 rc1 rc2 rc3 rc5 rc6 rcS init.d init 系统启动超级进程 inittab 进程启动配置文件 rc0 - rc6 各启动级别的启动脚本 ...
- Delphi ScrollBar组件