Peter Matseykanets

Results 22 comments of 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?

In the case of projects when a project is being created ![Image](https://github.com/user-attachments/assets/da5c37d7-3ebe-4530-8dec-da7fd097dc47) we want to see ![Image](https://github.com/user-attachments/assets/6922626a-2c45-4643-b247-5dba2e522d43) rather than what we see today ![Image](https://github.com/user-attachments/assets/a048bec9-acdb-4d91-aba4-c9cf60f35808)

For clusters we'd like to see ![Image](https://github.com/user-attachments/assets/2f9afd7c-1391-4d29-aa04-d44262651d74) ![Image](https://github.com/user-attachments/assets/9b867edc-ee86-4e1a-9db1-e67c8ce0fdb0)