-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[release/1.6] Fix memory leak with kubectl exec
>= 1.30.0
#10574
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
[release/1.6] Fix memory leak with kubectl exec
>= 1.30.0
#10574
Conversation
SHA: 60c4c2b2521fb454ce69dee737e3eb91a25e0535 Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Wondering if these should be an |
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Done! thanks @thaJeztah |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to the review of the borrow/sync PR on 1.7, code review looks good to me appears to not introduce new bad behavior :-) just need to sanity test against older k8s clients
As with 1.7 I also suppose a sanity check v1.23 min through 1.31 is needed, for 1.6, each time we change out the streaming protocol code base..
tested the following crictl versions. Note that the 1.30.0 and up has both protocols, so tested both.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
kubectl exec
>= 1.30.0
xref: #10568
xref: kubernetes/kubernetes#126608
Fix for panic in the issues logged above are already in latest kubernetes master specifically in staged repositories. Unfortunately both 1.6 and 1.7 are on really old versions of k8s and it's not feasible/practical to move to newer versions of k8s. So we instead copy over the
wsstream
package which has the fix and change references in our code to the copy here.