kubeadm 卸载 flannel

最新推荐文章于 2025-04-22 11:56:02 发布
最新推荐文章于 2025-04-22 11:56:02 发布
阅读量4.3k 收藏 3
点赞数 1
分类专栏： #flannel 文章标签： kubeadm flannel
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/oceanyang520/article/details/103901624
版权

1、找到之前的flannel yaml 的文件，执行：

kubectl delete -f xxxx.yaml

 

2、删除cni配置文件

rm -rf /etc/cni/net.d/*

 

3、重启kubelet ，不行的话重启服务器 reboot

systemctl restart kubelet

 

然后查看 kubectl get pod -n kube-system

flannel已经消失

卸载flannel安装kube-router网络插件
qq_43657581的博客
08-15 2012
1、在master节点中删除flannel kubectl delete -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml rm -rf /etc/cni/net.d/* 2、在node节点清理flannel网络插件 systemctl restart ku...
kubeadm安装的k8s集群卸载方式
weixin_43196631的博客
09-03 2816
kubeadm安装的k8s集群卸载方式 # 卸载服务 ``` kubeadm reset ``` # 删除rpm包 ``` rpm -qa|grep kube*|xargs rpm --nodeps -e ``` # 删除容器及镜像 ``` docker images -qa|xargs docker rmi -f ``` #清理配置信息 ``` rm -rf /etc/cni/net.d rm -rf $HOME/.kube/config rm -rf /etc/kubernetes/ rm -rf /v
K8S安装网络插件flannel问题修复(cni plugin not initialized)
crabdave的博客
04-29 6754
K8S安装网络插件问题修复。error: cni plugin not initialized。看不到cni0的问题，SystemdCgroup，/etc/containerd/config.toml
【Kubernetes】Kubernetes 网络插件 Flannel/Calico/Cilium
最新发布
mm1234556的博客
04-22 1148
这是一篇关于 K8s 网络插件（Flannel/Calico/Cilium）的文章！
flannel完全卸载
qq_54738879的博客
05-11 1167
删除flannel和cni网卡 删除flannel和cni相关目录 重启kubelet kubeadm: rancher:
k8s卸载flannel网络
weixin_34409741的博客
04-21 5114
在工作中，由于不同的需求，需要更换CNI插件；此场景为，卸载flannel网络，更换为calico网络；建议：在生产场景中，建议提前规划好k8s的网络，如果中途更换网络插件，产生的影响会比较大；卸载flannel网络步骤：#第一步，在master节点删除flannel kubectldelete-fhttps://raw.githubusercontent.com/co...
K8s卸载清理&flannel插件清理
简云的博客
08-03 4016
K8s相关目录清理 yum remove -y kubelet kubeadm kubectl kubeadm reset -f modprobe -r ipip lsmod rm -rf ~/.kube/ rm -rf /etc/kubernetes/ rm -rf /etc/systemd/system/kubelet.service.d rm -rf /etc/systemd/system/kubelet.service rm -rf /usr/bin/kube* rm -rf /etc/cni rm
linux卸载flannel服务,记录替换calico为flannel的过程
weixin_39678451的博客
05-05 1068
背景之前一内网测试环境，因想尝试下使用calico，所以安装calico作为kubernetes的网络插件，最近发现kubelet日志频繁报错，大致格式如下：StopPodSandbox $SHA from runtime service failed: rpc error: code = 2 desc = NetworkPlugin cni failed to teardown pod net...
使用kubeadm在ububtu16.04安装kubernetes1.5.5-flannel
ximenghappy的专栏
04-01 4049
kubernetes是Google开源的基于Docker的容器集群管理系统，是谷歌内部大规模集群管理系统Borg的开源版本。kubernetes基于Borg集群软件模型。 Kubernetes(K8s)是一个真正的平台，提供运行环境，使得复杂要求的应用在上面构建。它通过yaml语言写的配置文件，很简单快速的就能自动通过Docker镜像部署好应用环境，支持应用横向扩展，并且可以组织、编排、管理和迁移
Kubernetes (k8s 1.23) 安装与卸载
m0_60028455的博客
07-21 2349
镜像下载、域名解析、时间同步请点击 阿里云开源镜像站 请注意k8s在1.24版本不支持docker容器，本文使用kubeadm进行搭建 1.查看系统版本信息以及修改配置信息 1.1 安装k8s时，临时关闭swap ，如果不关闭在执行kubeadm部分命令会报错 swapoff -a或直接注释swap（需要重启生效） [root@hhdcloudrd7 /]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Tue Apr 19 11:43:1
基于kubeadm快速部署kubernetes K8S V1.17.4集群-无坑完整版
踏歌行的专栏
07-29 4254
基于kubeadm快速部署kubernetes K8S V1.17.4集群，并部署Dashboard Web页面，实现可视化查看Kubernetes资源
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
flannel网络的安装和删除
架构+开发+运维
08-10 2075
前言： k8s的部署，见以下两篇文档 《k8s1.20搭建抛弃docker使用containerd》 《k8s-1.21高可用集群搭建》 1. 安装 yml文件 1.21使用这个yml文件有警告，接口之后版本将弃用，但是1.21还是可以用的。 --- apiVersion: policy/v1beta1 kind: PodSecurityPolicy metadata: name: psp.flannel.unprivileged annotations: seccomp.secur.
清除 flannel 网络
xiliangMa的博客
10-30 4566
清除 flannel 网络 ifconfig cni0 down ifconfig flannel.1 down ifconfig del flannel.1 ifconfig del cni0 ip link del flannel.1 ip link del cni0 如果没有 brctl 命令 yum install bridge-utils brctl delbr flannel....
kubernetes使用flannel网络插件服务状态显示CrashLoopBackOff
无锋剑
08-23 4883
使用Kubeadm安装K8s集群，在安装flannel网络插件后，发现pod: kube-flannel-ds 一直是CrashLoopBackOff 报错内容如下： log is DEPRECATED and will be removed in a future version. Use logs instead. I0823 03:28:21.342352 1 main.go:5...
[kubernates]kube-flannel-ds 一直 CrashLoopBackOff
唧唧の歪歪的博客
11-04 6242
使用 Kubeadm 安装 K8s 集群，在安装 flannel 网络插件后，发现 kube-flannel-ds 一直处于 CrashLoopBackOff 状态： [root@test-129-70 k8s]# kubectl get po -A NAMESPACE NAME READY STATUS R...
Linux安装系列：Kubernetes集群安装及卸载（一主两从）
CancerKing的博客
01-07 809
Linux安装系列：Kubernetes集群安装及卸载（一主两从）
K8s集群里 中Flannel的状态显示为CrashLoopBackOff 时
qq_40914472的博客
08-09 739
K8s集群里 中Flannel的状态显示为CrashLoopBackOff 时，查看Flannel log日志显示：Error registering network: failed to acquire lease: subnet "10.244.0.0/16" specified in the flannel net config doesn't contain "172.16.4.0/24" PodCIDR of the "node1" node
k8s node节点断电重启出问题；flannel重启失败 CrashLoopBackOff；flannel pod报错"Back-off restarting failed container" ；
SeptDays的博客
02-17 5875
问题 如100字的题 产生原因 kubeadm装了k8s（各项指标正常） 结果电脑蓝屏重启；kubectl get nodes查看发现node节点都处于not ready状态。 解决过程 进入节点，查看systemctl status docker; systemctl status kubelet;发现docker好的，kubelet挂了。 （如果docker挂了且一直卡st...
Kubernetes集群搭建完全指南：基于Kubeadm
- 首先，你需要清理已有的Docker环境，这通常涉及卸载旧版本。 - 如果遇到包冲突错误，可以通过`yum remove`手动删除冲突的包。 - 安装18.06.1版本的Docker，使用相应的YUM命令。 二、Docker环境构建 1. 在所有...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值