Experiencing Intermittent Endpoint Errors Upon Update (Cilium)
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What happened**:
Days after upgrading, it was noticed some deployments were arriving slowly and would error for a while before clearing and starting.
```
Unable to assert if endpoint BPF programs need to be reloaded" ciliumEndpointName=/-0 endpoint=lxc1dd4209244f1 endpointID=205 error="unable to find endpoint link by name: Link not found"
```
**What you expected to happen**:
No issues after upgrade.
**How to reproduce it (as minimally and precisely as possible)**:
0.22.2 -> 0.22.5
Upgrade cluster to new eks-a version, causing a cilium upgrade. spawn a deployment.
**Anything else we need to know?**:
There is a ticket opened with Cilium for this: https://github.com/cilium/cilium/issues/31327
The suggestion is to upgrade to the current release.
**Environment**:
- EKS Anywhere Release: 0.22.5
- EKS Distro Release: bottlerocket-v1.31.7-kubernetes-1-31-eks-20
Contributor guide
Research direction
No repository file or test is named. Start with the linked Cilium issue #31327 and the reported 0.22.2 to 0.22.5 upgrade path, then reproduce the deployment behavior on EKS Anywhere. Done means confirming whether upgrading to the current release prevents the intermittent endpoint errors or identifying a repository change needed to address them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100