generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 320
Open
Labels
externalAn issue, bug or feature request filed from outside the AWS orgAn issue, bug or feature request filed from outside the AWS org
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=<redacted>/<redacted>-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: cilium/cilium#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
Metadata
Metadata
Assignees
Labels
externalAn issue, bug or feature request filed from outside the AWS orgAn issue, bug or feature request filed from outside the AWS org