fleet: Fleet 0.6.0 shipped with Rancher 2.7.3 still problems with kubeVersion

Is there an existing issue for this?

I have searched the existing issues

Current Behavior

I installed Rancher 2.7.3 fresh and charts like Longhorn (1.4.1) (and others) are failing with:

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

I did see issue rancher/fleet#399 which was just closed out hours ago, but it seems that 2.7.3 still has version 0.6.0 of the fleet controller where this issue is identified.

(Installing the Longhorn with the same values via Marketplace works just fine)

Expected Behavior

It should read the real kubernetes versions so it doesn’t break various charts (so far, Longhorn, Hashicorp Vault).

Steps To Reproduce

Install Rancher 2.7.3 on RKE2 1.25.7
Create a fleet.yaml with the below values and add to Continuous Delivery

defaultNamespace: longhorn-system
helm:
  releaseName: longhorn
  chart: longhorn
  repo: https://charts.longhorn.io
  version: 1.4.1

Environment

- Architecture: amd64
- Fleet Version: 0.6.0
- Cluster:
  - Provider: RKE2
  - Options:
  - Kubernetes Version: 1.25.7

Logs

No response

Anything else?

No response

About this issue

Original URL
State: closed
Created a year ago
Comments: 15 (2 by maintainers)

Most upvoted comments

Just in case, rancher 2.7.5 seems to have fleet 0.7.0 installed:

❯ k get apps -n cattle-system
NAME              CHART             VERSION         RELEASE NAME      RELEASE VERSION   STATUS
rancher           rancher           2.7.5           rancher           1                 deployed
rancher-webhook   rancher-webhook   2.0.5+up0.3.5   rancher-webhook   1                 deployed

❯ k get apps -n cattle-system -n cattle-fleet-system
NAME        CHART       VERSION           RELEASE NAME   RELEASE VERSION   STATUS
fleet       fleet       102.1.0+up0.7.0   fleet          2                 deployed
fleet-crd   fleet-crd   102.1.0+up0.7.0   fleet-crd      1                 deployed

e-minguez on Jul 3, 2023

@wagnst I tried the following on a parallel rancher test cluster and it seems to work…

helm -n cattle-fleet-system upgrade --create-namespace --wait    fleet-crd https://github.com/rancher/fleet/releases/download/v0.7.0-rc.2/fleet-crd-0.7.0-rc.2.tgz
helm -n cattle-fleet-system upgrade --create-namespace --wait    fleet https://github.com/rancher/fleet/releases/download/v0.7.0-rc.2/fleet-0.7.0-rc.2.tgz

That’s just a temporary patch though … It was enough for me to prove that an upgrade will help. That is why I asked when will the patch lands in a stable version of Rancher… This issue right now is leaving us with no choice but to manually patch or deploy some helm chart to manage our clusters … That’s suboptimal …

funilrys on May 19, 2023

Is there a workaround that will allow us to solve the issue ? (as for now we can’t create rke2 clusters

Hello! 0) Create RKE2 cluster (empty)
1. Run command for joining 1st Master (don't wait and get to the second step)

2. Run command for joining 1st Worker. You will see 1st Master change his status from WaitingNodeRef

3. Run command on 2nd and 3rd masters. After that cattle-cluster agents will come up and Worker1 change its status from WaitingNodeRef

4. Join other workers
Good luck!

Hi @daemonadmin Sorry for my late reply… It’s a very weird issue nevertheless your magic worked like a charm ! Thank you very much for your help ^^

rectacoda on Nov 6, 2023

@manno Sorry for the bump, but when will it land into a stable version of Rancher 2.7 ?

This is real trouble since I can’t upgrade to v2.7.5-rc1 … I’m running 2.7.3 right now - too 😞 And I don’t feel like it’s a good idea to update fleet myself …

funilrys on May 16, 2023