cni | 易学教程

Kubernets PODs running on different host, not able to establish TCP connection

阅读更多关于 Kubernets PODs running on different host, not able to establish TCP connection

问题 I have Kubernets 1.20.1 cluster with single master and single worker configured with ipvs mode. Using calico CNI calico/cni:v3.16.1 . Cluster running on OS RHEL 8 kernel 4.18.0-240.10 with firewalld and selinux disabled. Running one netshoot pod ( 10.1.30.130 ) on master and another pod ( 10.3.65.132 ) in worker node. I can ping both pod, in both direction if run the nc command in web server mode, connection is not working. I tried to run nginx on both server, not able get http traffic one

基于Kubeadm的Flannel分析

阅读更多关于基于Kubeadm的Flannel分析

Flannel概述 Flannel是将多个不同子网（基于主机Node）通过被Flannel维护的Overlay网络拼接成为一张大网来实现互联的，通过官方的一张网络拓扑图我们可以对其基本原理一目了然：值得探讨的是，flannel的这个overlay网络支持多种后端实现，除上图中的UDP，还有VXLAN和host-gw等。此外，flannel支持通过两种模式来维护隧道端点上FDB的信息，其中一种是通过连接Etcd来实现，另外一种是直接对接K8S，通过K8S添加删除Node来触发更新。 Flannel部署常见问题 1. Node状态显示为“NotReady” 我的K8S环境使用kubeadm来容器化运行K8S的各个组件（除kubelet直接运行在裸机上外），当我使用kubeadm join命令加入新的Minion Node到K8S集群中后，通过kubectl get node会发现所有的node都还是not ready状态，这是因为还没有配置好flannel网络。 2. 使用kube-flannel.yml无法创建DaemonSet 我使用的是K8S的1.6.4的版本，然后按照官方的说明，使用kube-flannel.yml来创建flannel deamon set，结果始终报错。正确的姿势是先使用kube-flannel-rbac

network plugin is not ready: cni config uninitialized

阅读更多关于 network plugin is not ready: cni config uninitialized

问题 KubeletNotReady runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized I don't know how to make the network plugin ready 回答1: While you run kubectl describe node <node_name> In the Conditions table, the Ready type will contain this message if you did not initialized cni . Proper initialization can be obtained by installing network addon. I will point you to 2 most used: Weave and Flannel 1) Weave $

Container runtime network not ready: cni config uninitialized

阅读更多关于 Container runtime network not ready: cni config uninitialized

问题 I'm installing kubernetes(kubeadm) on centos VM running inside Virtualbox , so with yum I installed kubeadm, kubelet and docker . Now while trying to setup cluster with kubeadm init --pod-network-cidr=192.168.56.0/24 --apiserver-advertise-address=192.168.56.33/32 i run into the following error : Unable to update cni config: No networks found in /etc/cni/net.d Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni