k3s v1.28/Rancher 2.8.3 : chart requires kubeVersion: >=1.22.0-0 which is incompatible with Kubernetes v1.20.0

[R-Nabil]

Welcome!

• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?

28

What version of Traefik are you using?

28

What did you do?

Hi all,

Upgraded my helm chart to 28 (i'm deploying using Fleet in Rancher). And i'm getting this error.
Is there anything i'm doing wrong ? It tells me version > 1.22 is required where my k3s is already 1.28

What did you see instead?

chart requires kubeVersion: >=1.22.0-0 which is incompatible with Kubernetes v1.20.0

What is your environment & configuration?

k3s v1.28
Rancher 2.8.3
Fleet 0.9.4

Additional Information

No response

[darkweaver87]

Hello @R-Nabil ,

I'm sorry to read you experience some troubles upgrading this chart.
Per this PR the requirements have been updated.

Would you mind to share the output of the following command, your kube context pointing to the cluster you mention:

kubectl version

Thanks.

Rémi

[R-Nabil]

Hello @R-Nabil ,

I'm sorry to read you experience some troubles upgrading this chart. Per this PR the requirements have been updated.

Would you mind to share the output of the following command, your kube context pointing to the cluster you mention:

kubectl version

Thanks.

Rémi

Of course not. Thank you for taking the time to answer and help.

Is thit what you needed ?

Client Version: v1.30.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.2+k3s1
WARNING: version difference between client (1.30) and server (1.28) exceeds the supported minor version skew of +/-1

[darkweaver87]

Hum, that's weird indeed :-/
Which version of helm (helm version) are you using ? We will try to reproduce and fix it ...
Thanks !

[R-Nabil]

Its actually done through Rancher Fleet (0.9.4) directly.

[R-Nabil]

Hi.

This issue can be closed. The error message was a red-herring. The issue was actually due to a middleware I use.
Once that was corrected, all flew through correctly.

Again appreciate your time in trying to help!

[darkweaver87]

OK I'm happy you solved. I'm sorry I set up a fleet environment this morning but I didn't have the chance to test :-)

[R-Nabil]

The fact you tried is honestly greatly appreciated Thanks again

…

On 16 May 2024 at 23:51 +0800, Rémi BUISSON ***@***.***>, wrote: OK I'm happy you solved. I'm sorry I set up a fleet environment this morning but I didn't have the chance to test :-) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: ***@***.***>