Peter Matseykanets
Peter Matseykanets
Upgrading to Go (to 1.20) has nothing to do with the CVE and will be done separately.
We need to make sure v2.7.11 changes are back-ported to v2.7 to bring Go to 1.20 and k8s to 1.27 https://github.com/rancher/rancher/blob/dfa8ae746283d1a11013abba59c0bb819ef7ba80/go.mod#L3
Once the new kube-api-auth version is tagged we'll need to bump it in rancher for supported release lines.
New kube-api-auth release tagged https://github.com/rancher/kube-api-auth/releases/tag/v0.2.1 with CVE fixes.
It seems like system-agent also requires fixing https://github.com/rancher/system-agent/blob/df30d89b07ec7b0ddab6de2d490a4c80798b258f/go.mod#L3
## Validation Template ## What was fixed, or what change have occurred kube-api-auth: - Library `golang.org/x/net` updated to v0.17.0 - Go version updated to 1.21 - k8s libraries (client-go, apiserver,...
Would it be possible to use English so that everybody understands?
@cyrilis Thanks!
In the case of projects when a project is being created  we want to see  rather than what we see today 
For clusters we'd like to see  