[Bug] Can't install on GKE

[Janrupf]

Search before asking

• I had searched in the issues and found no similar issues.

Version

25.5.1

What's Wrong?

The helm Chart version check fails even though the cluster is compatible:

error: failed to create chart from template: chart requires kubeVersion: >= 1.19 which is incompatible with Kubernetes v1.33.1-gke.1386000

What You Expected?

The helm chart should install successfully

How to Reproduce?

1. Create a GKE cluster with the kubernetes version from above
2. Attempt to install the doris-operator helm chart

Anything Else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[intelligentfu8]

The helm version is out of date. This is not chart's bug, please refer this helm issue to find result helm/helm#11751

[matiasbertani]

Could it be possible to remove the kubeVersion field from the Charts.yaml or maybe change it ? I'm having the same error with EKS:

Helm install failed for release doris/doris with chart doris-operator@25.7.0: chart requires kubeVersion: >= 1.19 which is incompatible with Kubernetes v1.34.1-eks-3025e55

I pulled the chart and edited the kubeVersion and start working:

diff --git a/doris-operator/Chart.yaml b/doris-operator/Chart.yaml
index 11c3b90b2..fd643fa82 100644
--- a/doris-operator/Chart.yaml
+++ b/doris-operator/Chart.yaml
@@ -9,7 +9,7 @@ keywords:
 - database
 - olap
 - sharding
-kubeVersion: '>= 1.19'
+kubeVersion: '>= 1.19.0-0'
 maintainers:

[matiasbertani]

After further investigation, it seems clear that the issue is not with Helm itself but with how the chart defines its kubeVersion constraint.

Helm relies on Masterminds/semver for version comparison. According to both the Helm docs and the SemVer README (see the "Checking Version Constraints" section), version ranges do not match pre-release versions unless the constraint explicitly allows them.

EKS (and GKE) Kubernetes versions always include a pre-release suffix, e.g.: v1.34.1-eks-3025e55. So, with a constraint like >= 1.19, SemVer will not consider pre-release versions valid, so Helm rejects the chart even though the Kubernetes version is technically higher.

The SemVer documentation explains that to include pre-releases in a version range, you must add a -0 suffix: >= 1.19.0-0

After changing the chart’s kubeVersion to include .0-0, Helm correctly accepted the EKS version.

[matiasbertani]

cc @intelligentfu8