Skip to content
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

bug(containerd): 1.7.11 has memory leak for kubectl exec fixed in 1.7.21 #1999

Open
robert-heinzmann-logmein opened this issue Oct 8, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@robert-heinzmann-logmein

What happened:

We observed a memory leak when using kubectl exec >= 1.30 for containerd older then 1.7.21. The upstream bug for this is containerd/containerd#10568. The issue seems to be fixed in https://github.com/containerd/containerd/releases/tag/v1.7.21 and https://github.com/containerd/containerd/releases/tag/v1.6.36. Current AMI is still at 1.7.11.

(See containerd/containerd#10568 (comment))

What you expected to happen:

No memory leak

How to reproduce it (as minimally and precisely as possible):

Repeated kubectl exec

Environment:

  • AWS Region: us-east-1
  • Instance Type(s): c5.large
  • Cluster Kubernetes version: 1.29
  • Node Kubernetes version: 1.29
  • AMI Version:
@robert-heinzmann-logmein robert-heinzmann-logmein added the bug Something isn't working label Oct 8, 2024
@cartermckinnon
Copy link
Member

You can mitigate this issue by using an older kubectl. If your control plane is on 1.29, you should be using the latest kubectl on that release branch.

We'll be updating containerd to 1.7.22 shortly: #1998

@Issacwww
Copy link
Member

#1998 has been released in v20241011 for AL2 based AMI
#2008 fix for AL23 will be in next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants