k8s 安装pod网络插件（flannel）报错

最新推荐文章于 2024-04-23 16:59:28 发布
最新推荐文章于 2024-04-23 16:59:28 发布
阅读量4.2k 收藏 6
点赞数 2
分类专栏： k8s 运维 文章标签： 运维 linux k8s
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_51720711/article/details/120047138
版权
运维 同时被 2 个专栏收录
26 篇文章 2 订阅
订阅专栏
k8s
4 篇文章 0 订阅
订阅专栏 
[root@master k8s]# kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/a70459be0084506e4ec919aa1c114638878db11b/Documentation/kube-flannel.yml
The connection to the server raw.githubusercontent.com was refused - did you specify the right host or port?
[root@master k8s]# kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
The connection to the server raw.githubusercontent.com was refused - did you specify the right host or port?

基本上是因为连不上外网导致，所以我们添加映射

199.232.68.133 raw.githubusercontent.com

但是还是报错

[root@master k8s]# kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/a70459be0084506e4ec919aa1c114638878db11b/Documentation/kube-flannel.yml
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/a70459be0084506e4ec919aa1c114638878db11b/Documentation/kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp [::1]:8080: connect: connection refused
[root@master k8s]# kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp [::1]:8080: connect: connection refused

所以我们采用先下载文件的方式

[root@master k8s]# wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
--2021-09-01 18:46:36--  https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
正在解析主机 raw.githubusercontent.com (raw.githubusercontent.com)... 199.232.68.133
正在连接 raw.githubusercontent.com (raw.githubusercontent.com)|199.232.68.133|:443... 已连接。

没有下文了，反复尝试，终于下载成功

[root@master k8s]# wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
--2021-09-01 19:03:14--  https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
正在解析主机 raw.githubusercontent.com (raw.githubusercontent.com)... 199.232.68.133
正在连接 raw.githubusercontent.com (raw.githubusercontent.com)|199.232.68.133|:443... 已连接。
已发出 HTTP 请求，正在等待回应... 200 OK
长度：4813 (4.7K) [text/plain]
正在保存至: “kube-flannel.yml”

100%[=====================================================================================>] 4,813       --.-K/s 用时 0s      

2021-09-01 19:03:14 (93.4 MB/s) - 已保存 “kube-flannel.yml” [4813/4813])

[root@master k8s]# ls
kube-flannel.yml

结果应用时又报错

[root@master k8s]# kubectl apply -f kube-flannel.yml 
unable to recognize "kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp [::1]:8080: connect: connection refused
unable to recognize "kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp [::1]:8080: connect: connection refused
unable to recognize "kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp [::1]:8080: connect: connection refused
unable to recognize "kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp [::1]:8080: connect: connection refused
unable to recognize "kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp [::1]:8080: connect: connection refused
unable to recognize "kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp [::1]:8080: connect: connection refused
[root@master k8s]# ll

解决方法

[root@master k8s]#  mkdir -p $HOME/.kube
[root@master k8s]#   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@master k8s]#   sudo chown $(id -u):$(id -g) $HOME/.kube/config
[root@master k8s]# kubectl apply -f kube-flannel.yml 
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
daemonset.extensions/kube-flannel-ds-amd64 created
daemonset.extensions/kube-flannel-ds-arm64 created
daemonset.extensions/kube-flannel-ds-arm created
daemonset.extensions/kube-flannel-ds-ppc64le created
daemonset.extensions/kube-flannel-ds-s390x created

搞定

还行少年
关注
  • 2
    点赞
  • 踩
  • 6
    收藏
    觉得还不错? 一键收藏
  • 3
    评论
专栏目录
k8s节点部署网络插件flannel.yaml
07-26
k8s节点部署网络插件flannel.yaml
flannel安装报错
Fly_鹏程万里
12-31 1395
所遇问题 The connection to the server localhost:8080 was refused - did you specify the right host or port? 解决方法 具体原因：kubenetes master没有与本机绑定，集群初始化的时候没有设置 解决方法： Step 1：编辑文件/etc/profile并在底部增加新的环境变量 export KUBECONFIG=/etc/kubernetes/admin.conf Ste.
kubeadmin搭建自建k8s集群
最新发布
xiaogg3678的专栏
04-23 966
kubeadmin搭建自建k8s集群
【k8s】节点flannel报错
oni1989的博客
09-22 448
Failed to find any valid interface to use: failed to get default interface: Unable to find default route
kube-flannel.yml
08-11
--- apiVersion: extensions/v1beta1 kind: PodSecurityPolicy metadata: name: psp.flannel.unprivileged annotations: seccomp.security.alpha.kubernetes.io/allowedProfileNames: docker/default seccomp.security.alpha.kubernetes.io/defaultProfileName: docker/default apparmor.security.beta.kubernetes.io/allowedProfileNames: runtime/default apparmor.security.beta.kubernetes.io/defaultProfileName: runtime/default spec: privileged: false volumes: - configMap - secret - emptyDir - hostPath allowedHostPaths: - pathPrefix: "/etc/cni/net.d" - pathPrefix: "/etc/kube-flannel" - pathPrefix: "/run/flannel" readOnlyRootFilesystem: false # Users and groups runAsUser: rule: RunAsAny supplementalGroups: rule: RunAsAny fsGroup: rule: RunAsAny # Privilege Escalation allowPrivilegeEscalation: false defaultAllowPrivilegeEscalation: false # Capabilities allowedCapabilities: ['NET_ADMIN'] defaultAddCapabilities: [] requiredDropCapabilities: [] # Host namespaces hostPID: false hostIPC: false hostNetwork: true hostPorts: - min: 0 max: 65535 # SELinux seLinux: # SELinux is unsed in CaaSP rule: 'RunAsAny' --- kind: ClusterRole apiVersion: rbac.authorization.k8s.io/v1beta1 metadata: name: flannel rules: - apiGroups: ['extensions'] resources: ['podsecuritypolicies'] verbs: ['use'] resourceNames: ['psp.flannel.unprivileged'] - apiGroups: - "" resources: - pods verbs: - get - apiGroups: - "" resources: - nodes verbs: - list - watch - apiGroups: - "" resources: - nodes/status verbs: - patch --- kind: ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1beta1 metadata: name: flannel roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: flannel subjects: - kind: ServiceAccount name: flannel namespace: kube-system --- apiVersion: v1 kind: ServiceAccount metadata: name: flannel namespace: kube-system --- kind: ConfigMap apiVersion: v1 metadata: name: kube-flannel-cfg namespace: kube-system labels: tier: node app: flannel data: cni-conf.json: | { "name": "cbr0", "plugins": [ { "type": "flannel", "delegate": { "hairpinMode": true, "isDefaultGateway": true } }, { "type": "portmap", "capabilities": { "portMappings": true } } ] } net-conf.json: | { "Network": "10.244.0.0/16", "Backend": { "Type": "vxlan" } } --- apiVersion: extensions/v1beta1 kind: DaemonSet metadata: name: kube-flannel-ds-amd64 namespace: kube-system labels: tier: node app: flannel spec: template: metadata: labels: tier: node app: flannel spec: hostNetwork: true nodeSelector: beta.kubernetes.io/arch: amd64 tolerations: - operator: Exists effect: NoSchedule serviceAccountName: flannel initContainers: - name: install-cni image: jmgao1983/flannel:v0.11.0-amd64 command: - cp args: - -f - /etc/kube-flannel/cni-conf.json - /etc/cni/net.d/10-flannel.conflist volumeMounts: - name: cni mountPath: /etc/cni/net.d - name: flannel-cfg mountPath: /etc/kube-flannel/ containers: - name: kube-flannel image: jmgao1983/flannel:v0.11.0-amd64 command: - /opt/bin/flanneld args: - --ip-masq - --kube-subnet-mgr resources: requests: cpu: "100m" memory: "50Mi" limits: cpu: "100m" memory: "50Mi" securityContext: privileged: false capabilities: add: ["NET_ADMIN"] env: - name: POD_NAME valueFrom: fieldRef: fieldPath: metadata.name - name: POD_NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace volumeMounts: - name: run mountPath: /run/flannel - name: flannel-cfg mountPath: /etc/kube-flannel/ volumes: - name: run hostPath: path: /run/flannel - name: cni hostPath: path: /etc/cni/net.d - name: flannel-cfg configMap: name: kube-flannel-cfg --- apiVersion: extensions/v1beta1 kind: DaemonSet metadata: name: kube-flannel-ds-arm64 namespace: kube-system labels: tier: node app: flannel spec: template: metadata: labels: tier: node app: flannel spec: hostNetwork: true nodeSelector: beta.kubernetes.io/arch: arm64 tolerations: - operator: Exists effect: NoSchedule serviceAccountName: flannel initContainers: - name: install-cni image: quay.io/coreos/flannel:v0.11.0-arm64 command: - cp args: - -f - /etc/kube-flannel/cni-conf.json - /etc/cni/net.d/10-flannel.conflist volumeMounts: - name: cni mountPath: /etc/cni/net.d - name: flannel-cfg mountPath: /etc/kube-flannel/ containers: - name: kube-flannel image: quay.io/coreos/flannel:v0.11.0-arm64 command: - /opt/bin/flanneld args: - --ip-masq - --kube-subnet-mgr resources: requests: cpu: "100m" memory: "50Mi" limits: cpu: "100m" memory: "50Mi" securityContext: privileged: false capabilities: add: ["NET_ADMIN"] env: - name: POD_NAME valueFrom: fieldRef: fieldPath: metadata.name - name: POD_NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace volumeMounts: - name: run mountPath: /run/flannel - name: flannel-cfg mountPath: /etc/kube-flannel/ volumes: - name: run hostPath: path: /run/flannel - name: cni hostPath: path: /etc/cni/net.d - name: flannel-cfg configMap: name: kube-flannel-cfg --- apiVersion: extensions/v1beta1 kind: DaemonSet metadata: name: kube-flannel-ds-arm namespace: kube-system labels: tier: node app: flannel spec: template: metadata: labels: tier: node app: flannel spec: hostNetwork: true nodeSelector: beta.kubernetes.io/arch: arm tolerations: - operator: Exists effect: NoSchedule serviceAccountName: flannel initContainers: - name: install-cni image: quay.io/coreos/flannel:v0.11.0-arm command: - cp args: - -f - /etc/kube-flannel/cni-conf.json - /etc/cni/net.d/10-flannel.conflist volumeMounts: - name: cni mountPath: /etc/cni/net.d - name: flannel-cfg mountPath: /etc/kube-flannel/ containers: - name: kube-flannel image: quay.io/coreos/flannel:v0.11.0-arm command: - /opt/bin/flanneld args: - --ip-masq - --kube-subnet-mgr resources: requests: cpu: "100m" memory: "50Mi" limits: cpu: "100m" memory: "50Mi" securityContext: privileged: false capabilities: add: ["NET_ADMIN"] env: - name: POD_NAME valueFrom: fieldRef: fieldPath: metadata.name - name: POD_NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace volumeMounts: - name: run mountPath: /run/flannel - name: flannel-cfg mountPath: /etc/kube-flannel/ volumes: - name: run hostPath: path: /run/flannel - name: cni hostPath: path: /etc/cni/net.d - name: flannel-cfg configMap: name: kube-flannel-cfg --- apiVersion: extensions/v1beta1 kind: DaemonSet metadata: name: kube-flannel-ds-ppc64le namespace: kube-system labels: tier: node app: flannel spec: template: metadata: labels: tier: node app: flannel spec: hostNetwork: true nodeSelector: beta.kubernetes.io/arch: ppc64le tolerations: - operator: Exists effect: NoSchedule serviceAccountName: flannel initContainers: - name: install-cni image: quay.io/coreos/flannel:v0.11.0-ppc64le command: - cp args: - -f - /etc/kube-flannel/cni-conf.json - /etc/cni/net.d/10-flannel.conflist volumeMounts: - name: cni mountPath: /etc/cni/net.d - name: flannel-cfg mountPath: /etc/kube-flannel/ containers: - name: kube-flannel image: quay.io/coreos/flannel:v0.11.0-ppc64le command: - /opt/bin/flanneld args: - --ip-masq - --kube-subnet-mgr resources: requests: cpu: "100m" memory: "50Mi" limits: cpu: "100m" memory: "50Mi" securityContext: privileged: false capabilities: add: ["NET_ADMIN"] env: - name: POD_NAME valueFrom: fieldRef: fieldPath: metadata.name - name: POD_NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace volumeMounts: - name: run mountPath: /run/flannel - name: flannel-cfg mountPath: /etc/kube-flannel/ volumes: - name: run hostPath: path: /run/flannel - name: cni hostPath: path: /etc/cni/net.d - name: flannel-cfg configMap: name: kube-flannel-cfg --- apiVersion: extensions/v1beta1 kind: DaemonSet metadata: name: kube-flannel-ds-s390x namespace: kube-system labels: tier: node app: flannel spec: template: metadata: labels: tier: node app: flannel spec: hostNetwork: true nodeSelector: beta.kubernetes.io/arch: s390x tolerations: - operator: Exists effect: NoSchedule serviceAccountName: flannel initContainers: - name: install-cni image: quay.io/coreos/flannel:v0.11.0-s390x command: - cp args: - -f - /etc/kube-flannel/cni-conf.json - /etc/cni/net.d/10-flannel.conflist volumeMounts: - name: cni mountPath: /etc/cni/net.d - name: flannel-cfg mountPath: /etc/kube-flannel/ containers: - name: kube-flannel image: quay.io/coreos/flannel:v0.11.0-s390x command: - /opt/bin/flanneld args: - --ip-masq - --kube-subnet-mgr resources: requests: cpu: "100m" memory: "50Mi" limits: cpu: "100m" memory: "50Mi" securityContext: privileged: false capabilities: add: ["NET_ADMIN"] env: - name: POD_NAME valueFrom: fieldRef: fieldPath: metadata.name - name: POD_NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace volumeMounts: - name: run mountPath: /run/flannel - name: flannel-cfg mountPath: /etc/kube-flannel/ volumes: - name: run hostPath: path: /run/flannel - name: cni hostPath: path: /etc/cni/net.d - name: flannel-cfg configMap: name: kube-flannel-cfg
kubernetes应用flannel失败 Connection refused.
xdmstar的专栏
11-29 1840
1.18.3K8S安装raw.githubusercontent.com无法连接问题 按照官网给的命令 kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml 回头查看k8s的运行状态，有一项卡在了这里 [root@server01 ~]# wget https://raw.githubusercontent.com/coreos/flannel/m
解决k8s无法安装flannel
ZhShy
02-20 1189
【代码】解决k8s无法安装flannel。
k8s二进制部署v1.22.15，flannel安装排错过程
MssGuo的博客
11-02 1720
这是因为没有安装网络插件。发现pod一致启动不了，一致处于失败，重启，失败，重启的状态。二进制部署的k8sv1.22.15，
CNI plugins v0.8.6，k8s安装flannel等插件下载
03-15
sed -i -r "s#quay.io/coreos/flannel:.*-amd64#lizhenliang/flannel:v0.12.0-amd64#g" kube-flannel.yml 默认镜像地址无法访问，修改为docker hub镜像仓库。 kubectl apply -f kube-flannel.yml
calico flannel k8s 安装yaml文件
03-05
在Kubernetes（k8s）集群中，网络插件起着至关重要的作用，它们负责为Pod之间提供网络通信。在本话题中，我们将探讨两个流行的网络插件：Calico和Flannel，以及如何通过YAML文件来安装它们。YAML是Kubernetes的主要...
k8s搭建Kubernetes（k8s）集群用到的部署CNI网络插件
02-21
问题场景：由于k8s安装master一直处于NotReady状态查看日志出现 failed to find plugin “flannel” in path [/opt/cni/bin]【CentOS7.9】(ps:不需要积分) 解决办法：下载CNI插件，在此提供amd和arm，其他可访问链接...
k8s网络插件kube-flannel.yml
08-04
k8s网络插件kube-flannel.yml
【K8S】节点kubectl报错The connection to the server localhost:8080 was refused
yujikang123的博客
05-19 8784
问题描述 在部署kubernetes之后，执行kubectl命令，无论是get nodes还是apply操作，Kubernetes报 The connection to the server localhost:8080 was refused 可能出现原因 出现这种问题的原因有两种 1、在任何节点上执行报错 出现这个问题的原因是kubectl命令需要使用kubernetes-admin的身份来运行，在“kubeadm int”启动集群的步骤中就生成了“/etc/kubernetes/admin.conf
Kubernetes The connection to the server localhost:8080 was refused - did you specify the right host
专注基础架构领域
01-28 3612
配置kubenetes的flannel网络的时候，出现以下报错 The connection to the server localhost:8080 was refused - did you specify the right host or port? 原因： kubenetes master没有与本机绑定，集群初始化的时候没有设置 解决办法（执行以下命令）： ...
wget https://raw.githubusercontent.com/.../kubeflannel.yml连接不上的粗暴解决方案
kk爱闹
10-13 1224
wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml拒绝连接或者连接不上的另一种解决方式
k8s V1.11.1报错：The connection to the server localhost:8080 was refused
小新没有蜡笔
09-19 1万+
问题描述： # 安装flannel插件时报错 root@test:~# kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/v0.10.0/Documentation/kube-flannel.yml unable to recognize "https://raw.githubusercontent.com/core...
解决Kubernetes的flannel pod出现Init:RunContainerError问题
ftzchina的博客
12-23 3433
一：故障背景 我们有个k8s集群，一个master节点和三个Node节点，其中node2的节点ping不通node1节点的pod ip。需要排查一下为什么ping不通pod ip的问题。 二：故障排查 1，三板斧第一斧 一般k8s的网络问题首先从网络组件开始查，本集群用的是flannel网络，在主节点上看看flannel的运行情况 命令： kubectl get po -o wide -n kube-system 有两个flannel的pod状态不对，处于Init:RunCo...
kubectl命令出现错误“The connection to the server localhost:8080 was refused”
热门推荐
star的博客
11-12 3万+
kubectl命令报错 “The connection to the server localhost:8080 was refused - did you specify the right host or port?” 解决方法： 1.将主节点（master）中的“/etc/kubernetes/admin.conf”文件拷贝到从节点相同目录下 2.配置环境变量 echo "export KUBECONFIG=/etc/kubernetes/admin.conf" >> ~/.bash_pr
namespace/kube-flannel created clusterrole.rbac.authorization.k8s.io/flannel created clusterrolebinding.rbac.authorization.k8s.io/flannel created serviceaccount/flannel created configmap/kube-flannel-cfg created daemonset.apps/kube-flannel-ds created
07-11
这些命令是在 Kubernetes 中创建 Flannel 网络插件所需的资源。以下是每个资源的解释： 1. namespace/kube-flannel: 创建一个名为 "kube-flannel" 的命名空间，用于隔离 Flannel 相关的资源。 2. clusterrole.rbac.authorization.k8s.io/flannel: 创建一个名为 "flannel" 的 ClusterRole，定义了 Flannel 所需的权限。 3. clusterrolebinding.rbac.authorization.k8s.io/flannel: 创建一个名为 "flannel" 的 ClusterRoleBinding，将 ClusterRole "flannel" 绑定到默认的 serviceaccount/flannel。 4. serviceaccount/flannel: 创建一个名为 "flannel" 的 ServiceAccount，用于授权 Flannel 访问 Kubernetes API。 5. configmap/kube-flannel-cfg: 创建一个名为 "kube-flannel-cfg" 的 ConfigMap，包含 Flannel 配置信息。 6. daemonset.apps/kube-flannel-ds: 创建一个名为 "kube-flannel-ds" 的 DaemonSet，它确保在每个节点上运行一个 Pod，该 Pod 包含 Flannel 容器和所需的网络配置。 这些资源的创建是为了在 Kubernetes 集群中部署和配置 Flannel 网络插件，以提供集群内部的网络通信和跨节点的 Pod 互联。通过这些资源的创建，Flannel 将在每个节点上自动部署并配置网络功能。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 3
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值