project-calico

问题 We're running a web API app on Kubernetes (1.9.3) in AWS (set with KOPS). The app is a Deployment and represented by a Service (type: LoadBalancer) which is actually an ELB (v1) on AWS. This generally works - except that some packets (fragments of HTTP requests) are "delayed" somewhere between the client <-> app container. (In both HTTP and HTTPS which terminates on ELB). From the node side : ( Note: Almost all packets on server-side arrive duplicated 3 times ) We use keep-alive so the tcp

问题 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

来源： https://stackoverflow.com/questions/60176343/how-to-make-the-pod-cidr-range-larger-in-kubernetes-cluster-deployed-with-kubead

来源： https://stackoverflow.com/questions/60176343/how-to-make-the-pod-cidr-range-larger-in-kubernetes-cluster-deployed-with-kubead

来源： https://stackoverflow.com/questions/60176343/how-to-make-the-pod-cidr-range-larger-in-kubernetes-cluster-deployed-with-kubead

问题 I'm running Kubernetes 1.13.2, setup using kubeadm and struggling with getting calico 3.5 up and running. The cluster is run on top of KVM. Setup: kubeadm init --apiserver-advertise-address=10.255.253.20 --pod-network-cidr=192.168.0.0/16 modified calico.yaml file to include: - name: IP_AUTODETECTION_METHOD value: "interface=ens.*" applied rbac.yaml , etcd.yaml , calico.yaml Output from kubectl describe pods : Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled

问题 I've network related issue on the Kubernetes host, using Calico network layer. For continuous integration I need to run docker in docker, but running simple docker build with this Dockerfile : FROM praqma/network-multitool AS build RUN route RUN ping -c 4 google.com RUN traceroute google.com produces output: Step 1/4 : FROM praqma/network-multitool AS build ---> 3619cb81e582 Step 2/4 : RUN route ---> Running in 80bda13a9860 Kernel IP routing table Destination Gateway Genmask Flags Metric Ref

问题 This is a Kubespray deployment using calico. All the defaults are were left as-is except for the fact that there is a proxy. Kubespray ran to the end without issues. Access to Kubernetes services started failing and after investigation, there was no route to host to the coredns service. Accessing a K8S service by IP worked. Everything else seems to be correct, so I am left with a cluster that works, but without DNS. Here is some background information: Starting up a busybox container: #

问题 I have CoreOS beta (1153.4.0) I'm trying to run calicoctl to check if my calico networking is properly configured. so I'm trying to run a calicoctl rkt container with the command rkt run quay.io/calico/ctl and I get the output image: using image from local store for image name coreos.com/rkt/stage1-coreos:1.13.0 image: using image from local store for image name quay.io/calico/ctl networking: loading networks from /etc/rkt/net.d networking: loading network default with type ptp [ 2147.433992]

问题 I'm trying to setup a zookeeper and kafka as separate Kubernetes deployments/pods in a shared namespace. I've bootstraped a local K8s 1.8 with Calico via kubeadm on my Ubuntu sandbox... For the Zookeeper, I'm using the image zookeeper:3.4 from hub.docker.com and I created a Kubernetes deployment and service, where I expose ports: 2181 2888 3888. Service name is zookeeper and I assume I should be able to use it by this hostname from the pods in the namespace. For the Kafka 1.0, I've created my