Fleet 0.6.0 shipped with Rancher 2.7.3 still problems with kubeVersion

Question

Fleet 0.6.0 shipped with Rancher 2.7.3 still problems with kubeVersion

bennysp opened this issue a year ago · comments

Ben Ptacek commented a year ago

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 #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

Matthew DeVenny · Answer 1 · Fri May 05 2023 23:03:21 GMT+0800 (China Standard Time)

Appears the fix is coming in 0.7.0
https://github.com/rancher/fleet/releases/tag/v0.7.0-rc.2

Mario Manno · Answer 2 · Tue May 09 2023 17:51:37 GMT+0800 (China Standard Time)

Yes, this should be fixed in 0.7.0

Nissar Chababy · Answer 3 · Tue May 16 2023 23:15:26 GMT+0800 (China Standard Time)

@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 ...

Steffen Wagner · Answer 4 · Thu May 18 2023 21:00:55 GMT+0800 (China Standard Time)

i'm running 2.7.5-rc1 but it still doesnt work. I am installing hashicorp/vault which has kubeVersion: ">= 1.22.0-0" listed in the chart.
Getting Chart requires kubeVersion: >= 1.22.0-0 which is incompatible with Kubernetes v1.20.0
Cluster runs on v1.25.9

Phillip Schichtel · Answer 5 · Thu May 18 2023 21:02:03 GMT+0800 (China Standard Time)

@manno To add to what @wagnst said: We had this issue before, but it (apparently temporarily) disappeared after the upgrade from rancher 2.6.x to 2.7.3, but it is back now. I think it started happening after upgrading my cluster to either 1.24.x or 1.25.x.

Phillip Schichtel · Answer 6 · Thu May 18 2023 21:19:39 GMT+0800 (China Standard Time)

nvm, we figured it out: the rancher k8s had disk pressure, which prevented the deployment of the new fleet.

Nissar Chababy · Answer 7 · Fri May 19 2023 16:11:03 GMT+0800 (China Standard Time)

@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 ...

Ben Ptacek · Answer 8 · Sat May 20 2023 12:57:54 GMT+0800 (China Standard Time)

Thanks @funilrys , that trick worked for me too.