mikekuzak

@snasovich any plans to line up the K8s supported versions with the UI ? I think there seems to be a gap here.

Provisoner : 1.24.0 with Rancher 2.5.14 Error: expected kubernetes_version to be one of [v1.22.4-rancher1-1 v1.21.7-rancher1-1 v1.21.6-rancher1-2 v1.21.6-rancher1-1 v1.21.5-rancher1-1 v1.21.4-rancher1-1 v1.20.13-rancher1-1 v1.20.12-rancher1-2 v1.20.12-rancher1-1 v1.20.11-rancher1-2 v1.20.11-rancher1-1 v1.20.10-rancher1-2 v1.20.10-rancher1-1 v1.20.9-rancher1-1 v1.20.8-rancher1-1 v1.20.6-rancher1-1 v1.20.5-rancher1-1...

Also interested

k8ssandra/k8ssandra#1447

Same issue when upgrading on Rancher via UI AppsV2 from 1.6.0 -> 2.0.0 Docker v20.10 K8s: v1.20 ``` helm upgrade --history-max=5 --install=true --namespace=elastic-system --reset-values=true --timeout=10m0s --values=/home/shell/helm/values-eck-operator-2.0.0.yaml --version=2.0.0 --wait=true eck-operator /home/shell/helm/eck-operator-2.0.0.tgz...

I'm doing this for the build version: ``` # Auto increment minor build version poetry version "$(poetry version -s).${BUILD_NR}" ``` Does the trick for us ``` Packaging ... Python 3.8.16...

Same issue ...

I have the same issue: k8ssandra Helm 1.4.1 (reaper version 3.0.0, now 3.1.1) K8s v1.20 cassandra 3.11.10 ``` cassandra: version: "3.11.10" allowMultipleNodesPerWorker: false cassandraLibDirVolume: storageClass: local-path size: 120Gi heap: size:...

> > Some repairs are working, but when the nodes get bounced it looks like it tries to connect to wrong IPs which don't exists anymore. > > Hey @mikekuzak....

> @MantiMantilla Thanks a lot for the detailed explanation, that really helps. Meanwhile I found a workaround that works: Replacing `micromamba` with `mamba`. > > `mamba` both has no problems...