Questions tagged [calico]
63 questions
0
votes
1 answer
Disable Source NAT for Calico
The default settings that kubeadm + calico use is to NAT any incoming connection that is not from a pod_ip.
I have calico publishing the service network to my outside LAN, and would rather the service pods utilize the actual client IPs and not a…
![](../../users/profiles/537147.webp)
Matt Ruge
- 1
- 1
0
votes
1 answer
For route command output, what does an asterisk under interface column mean?
For my Kubernetes nodes, I see following entry with a star under the interface column. I do not see this mentioned in "route" command's documentation. The only star mentioned there is for gateway. This entry has been created by Calico for the…
![](../../users/profiles/471893.webp)
user6317694
- 131
- 3
0
votes
1 answer
Kubernetes with Dual Stack on both Pod and Service level
I have 3 Ubuntu VMs where all of them have 2 interfaces. One interface with v4 address and other with both v4 and v6 address. 3 VMs are reachable from each other on all 3 (2 v4 and 1 v6) addresses.
I'm trying to install Kubernetes Cluster with…
![](../../users/profiles/237033.webp)
R Kaja Mohideen
- 111
- 4
0
votes
2 answers
Node-to-Node communication doesn't work with Kubernetes with Calico
I'm quite new to Kubernetes, event if it doesn't feel like after I spent dozens of hours trying to setup a working Kubernetes.
The edge parameters:
1 master and 3 nodes
set up using kubeadm
kubernetes version 1.12.1, Calico 3.2
Primary IP addresses…
![](../../users/profiles/152179.webp)
Daniel Alder
- 533
- 1
- 8
- 19
0
votes
0 answers
Calico CNI calio-apiserver issues, on-premises kubeadm based kubernetes v1.24.2 cluster
I am unable to get calico CNI fully functional on a on-premises kubeadm based kubernetes v1.24.2 cluster.
The calio-apiserver pods (in the calio-apiserver namespace) have the status "CrashLoopBackOff".
I installed calico CNI using the commands below…
![](../../users/profiles/158327.webp)
Allan K
- 111
- 2
0
votes
0 answers
kubeadm based kubernetes (v1.24.2) worker nodes are still in "NotReady" status even after installing calico CNI ("Error querying BIRD")
kubeadm based kubernetes (v1.24.2) worker nodes are still in "NotReady" status even after installing calico CNI ("dial unix /var/run/bird/bird.ctl: connect: no such file or directory")
I have deployed calico CNI on kubeadm based kubernetes cluster…
![](../../users/profiles/158327.webp)
Allan K
- 111
- 2
0
votes
1 answer
kubeadm based kubelet 1.24.2 calico CNI issues
I have installed a kubeadm based kubernetes cluster (v1.24.2) on Centos7.
I have attempted to install calico CNI as per the instructions at "https://projectcalico.docs.tigera.io/getting-started/kubernetes/quickstart".
The "/etc/cni/net.d/" and…
![](../../users/profiles/158327.webp)
Allan K
- 111
- 2
0
votes
0 answers
kubeadm based kubernetes Get "https://10.96.0.1:443/api?timeout=32s": dial tcp 10.96.0.1:443: connect: no route to host
I have deployed a kubeadm based kubernetes cluster v1.24.3 which consists of one control-plane node and 3 worker nodes (all Centos 7 VMs). These are all "on premises" on a single physical node.
On this setup, I am trying to deploy a CNI network…
![](../../users/profiles/158327.webp)
Allan K
- 111
- 2
0
votes
0 answers
Calico HA cluster - not-ready:NoSchedule
Installed Calico on a K8s HA cluster
Note: same installation worked on single node installation, removing taint. But in a HA Cluster it does only have taint: node.kubernetes.io/not-ready:NoSchedule
kubectl create -f…
![](../../users/profiles/726413.webp)
Chris G.
- 157
- 5
0
votes
1 answer
Calico Kubernetes Network Policy is denying all traffic and not working as expected
I am trying to implement some Calico based Kubernetes Network Policies. I have already setup Calico in my cluster and all the Calico based pods are running fine.
In my cluster, There are two pods.
1. An Nginx pod
2. An Apache pod
My requirement is…
![](../../users/profiles/947989.webp)
arjunbnair
- 25
- 1
- 2
- 8
0
votes
0 answers
Calico deployment not saving tolerance for master node
I was trying to setup a Kubernetes Cluster using Amazon EC2 and Kubeadm.
I created a 't2.large' EC2 instance based on Ubuntu 18.04 AMI. Setup kubeadm, kubelet, kubectl and docker as the container runtime.
Ran the kubeadm init…
![](../../users/profiles/947989.webp)
arjunbnair
- 25
- 1
- 2
- 8
0
votes
1 answer
How to re-trigger failed flannel to calico migration?
I have a 3 node kubernetes cluster with k8s 1.22 version with flannel setup and running fine. I did run live migration steps from flannel to calico as describes in here. Cluster migrated to calico successfully.
However when I tried multiple times,…
![](../../users/profiles/714196.webp)
Siddharood
- 61
- 5
0
votes
0 answers
Kubernetes: route traffic to a subnet via a pod (accesing management VPN clients from pods)
Given two pods deployed on different nodes:
myapp pod deployed on apps node
wireguard pod deployed on vpn node, using a subnet like 172.16.30.0/16
I need myapp to be able to be able to route traffic to the wireguard peers (VPN clients) having IPs…
![](../../users/profiles/91152.webp)
nemesisdesign
- 107
- 6
0
votes
1 answer
Kubernetes Cluster on CentOS 7 with kubeadm 1.24 - calico => coredns stuck in ContainerCreating
In order to install a master kubernetes node on centos7 with containerd and calico :
I followed this steps : https://computingforgeeks.com/install-kubernetes-cluster-on-centos-with-kubeadm/
After the kubeadm init --pod-network-cidr=192.168.0.0/16 …
![](../../users/profiles/967232.webp)
awot83
- 31
- 1
- 5
0
votes
0 answers
Trying to use a CNI configuration with Calico in Minikube with Helm
I am trying to configure a network configuration in our Kubernetes cluster via Helm with Calico, we are running minikube with calico like this:
minikube start --network-plugin=cni --cni=calico
And we include the network config like this:
# network…
![](../../users/profiles/179753.webp)
carlos.baez
- 101