-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CrashLoopBackOff on Calico and Canal #6
Comments
Calico uses {
"name": "k8s-pod-network",
"cniVersion": "0.3.1",
"plugins":
[
{
"type": "calico",
"log_level": "info",
"datastore_type": "kubernetes",
"nodename": "__KUBERNETES_NODE_NAME__",
"mtu": __CNI_MTU__,
"ipam": { "type": "calico-ipam" },
"policy": { "type": "k8s" },
"kubernetes": { "kubeconfig": "__KUBECONFIG_FILEPATH__" },
"container_settings": { "allow_ip_forwarding": true }, # ADD THIS
},
{
"type": "portmap",
"snat": true,
"capabilities": { "portMappings": true },
},
{ "type": "bandwidth", "capabilities": { "bandwidth": true } },
],
} The container should run normally. It works for me, and, I'm getting some logs from lb-port-80/lb-port-443 like below: + trap exit TERM INT
/usr/bin/entry: line 6: can't create /proc/sys/net/ipv4/ip_forward: Read-only file system
+ echo 1
+ true
+ cat /proc/sys/net/ipv4/ip_forward
+ '[' 1 '!=' 1 ]
+ iptables -t nat -I PREROUTING '!' -s 10.43.199.158/32 -p TCP --dport 80 -j DNAT --to 10.43.199.158:80
+ iptables -t nat -I POSTROUTING -d 10.43.199.158/32 -p TCP -j MASQUERADE
+ '[' '!' -e /pause ]
+ mkfifo /pause Anyway, my Ingress works normally and the status of lb-port-80/lb-port-443 is |
Thank you. This works. For future reference, in case other people might run into same problem, to test, I followed the instructions on https://docs.projectcalico.org/getting-started/kubernetes/k3s/quickstart, with the following changes:
|
k3s-io/klipper-lb#6 enable calico ip_forward setting Signed-off-by: Deshi Xiao <xiaods@gmail.com>
I'm just trying to give it a try, for an IPv6 only k3s cluster, I restart my with a fresh install on k3os 0.22.2 (k3s 1.22.2), i fall again on that svclb-traefik CrashLoopBackOff just after Calico install. ip_forward is setted to 1 on the node, but svclb-traefik always complain about it. @sauber An alternate way, to set the CNI to propagate ip_forward inside the pod, for the same result : |
Still holds true for the manifest approach (no idea about the operator mode, neither): gitpod proxy does not work without allowing ip forwarding which is disabled by default. Meanwhile I left traefik disabled. |
Same issue here. Using the operator, I just had to set |
When using Calico og Canal as the cluster network driver, klipper-lb fails to start up pods for LoadBalancer services.
From a default k3s installation on ubuntu 20.04 with only Flannel disabled, and either Calico or Canal added:
The text was updated successfully, but these errors were encountered: