-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[arm64] BGP Control Plane + Native Routing + LB-IPAM results in BPF program too large error (1.15-dev) #28651
Copy link
Copy link
Closed as not planned
Closed as not planned
Copy link
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.info-completedThe GH issue has received a reply from the authorThe GH issue has received a reply from the authorkind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.This was reported by a user in the Cilium community, eg via Slack.kind/complexity-issueRelates to BPF complexity or program size issuesRelates to BPF complexity or program size issuesstaleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Metadata
Metadata
Assignees
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.info-completedThe GH issue has received a reply from the authorThe GH issue has received a reply from the authorkind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.This was reported by a user in the Cilium community, eg via Slack.kind/complexity-issueRelates to BPF complexity or program size issuesRelates to BPF complexity or program size issuesstaleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Is there an existing issue for this?
What happened?
In this environment, Cilium decided that the BPF program is too large so it's rather unhappy as result.
Cilium Version
cilium-cli: v0.12.1 compiled with go1.18.5 on linux/amd64
cilium image (default): v1.12.0
cilium image (stable): v1.14.2
cilium image (running): -ci:0a28eb945e98a4729f5b580a28b5e346def975db
Kernel Version
6.1.0-12-arm64
6.1.0-9-arm64
Kubernetes Version
{ "clientVersion": { "major": "1", "minor": "27", "gitVersion": "v1.27.6", "gitCommit": "741c8db18a52787d734cbe4795f0b4ad860906d6", "gitTreeState": "archive", "buildDate": "2023-10-03T16:31:42Z", "goVersion": "go1.21.1", "compiler": "gc", "platform": "linux/amd64" }, "kustomizeVersion": "v5.0.1", "serverVersion": { "major": "1", "minor": "27", "gitVersion": "v1.27.4+k3s1", "gitCommit": "36645e7311e9bdbbf2adb79ecd8bd68556bc86f6", "gitTreeState": "clean", "buildDate": "2023-07-28T09:46:05Z", "goVersion": "go1.20.6", "compiler": "gc", "platform": "linux/arm64" } }Sysdump
The whole sysdump of my dev cluster (too large for GH): https://s3.skym.fi/public/cilium-sysdump-20231007-213830.zip
Relevant log output
Anything else?
Current helm values are available here: https://github.com/samip5/k3s-dev-cluster/blob/fde716e03d35bb617b68843bd50ea11fdda7eb5f/kubernetes/apps/kube-system/cilium/app/helmrelease.yaml
Code of Conduct