tunnel interfaces created by Calico are not being removed upon node deletion on sles15 machines

[riyazhakki]

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

1. create a worker node
2. submit a pod
3. delete the pod
4. delete the node

Context

Your Environment

• Calico version docker.io/calico/node:v3.26.0
• Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes 1.29
• Operating System and version: centos15
• Link to your project (optional):

[riyazhakki]

tried to enable cleanup feature with following yaml, recived error message error: resource mapping not found for name: "default" namespace: "" from "calico.yaml": no matches for kind "FelixConfiguration" in version "projectcalico.org/v3"

calico.yaml

apiVersion: projectcalico.org/v3 kind: FelixConfiguration metadata: name: default spec: cleanup: enabled: true

Configuration:10-calico.conflist

{ "name": "k8s-pod-network", "cniVersion": "0.3.1", "plugins": [ { "type": "calico", "log_level": "info", "log_file_path": "/var/log/calico/cni/cni.log", "datastore_type": "kubernetes", "nodename": "sworker", "mtu": 0, "ipam": { "type": "calico-ipam" }, "policy": { "type": "k8s" }, "kubernetes": { "kubeconfig": "/etc/cni/net.d/calico-kubeconfig" } }, { "type": "portmap", "snat": true, "capabilities": {"portMappings": true} }, { "type": "bandwidth", "capabilities": {"bandwidth": true} } ] }

[coutinhop]

@riyazhakki could you please fill in the issue template? And also give a bit more details on the commands you used to execute the steps you mentioned?

error: resource mapping not found for name: "default" namespace: "" from "calico.yaml": no matches for kind "FelixConfiguration" in version "projectcalico.org/v3"

This is caused by the apiserver not being deployed (please see https://docs.tigera.io/calico/latest/operations/install-apiserver#install-the-api-server). BUT, this manifest looks completely wrong, so even after you deploy the apiserver you're going to see further errors. There is no cleanup or configuration present in the spec for FelixConfiguration: https://docs.tigera.io/calico/latest/reference/resources/felixconfig#spec

May I ask where did you get that manifest from?

[riyazhakki]

@riyazhakki could you please fill in the issue template? And also give a bit more details on the commands you used to execute the steps you mentioned?

error: resource mapping not found for name: "default" namespace: "" from "calico.yaml": no matches for kind "FelixConfiguration" in version "projectcalico.org/v3"

This is caused by the apiserver not being deployed (please see https://docs.tigera.io/calico/latest/operations/install-apiserver#install-the-api-server). BUT, this manifest looks completely wrong, so even after you deploy the apiserver you're going to see further errors. There is no cleanup or configuration present in the spec for FelixConfiguration: https://docs.tigera.io/calico/latest/reference/resources/felixconfig#spec

May I ask where did you get that manifest from?

@coutinhop, Thank you for looking into this issue. As you suggested, I have completed the template and included the commands used to reproduce the issue.

The manifest I mentioned is obtained from the path /etc/cni/net.d/10-calico.conflist.