When some fields like CONTROL_PLANE_HOST are set to null or emtpy, the helm 4.0 chart installation returns the following error:
oneadmin@llm-test-env:~$ helm install --kubeconfig ./kubeconfig_management.yaml \
k8s-gpu-test capone/capone-rke2 \
--values ./values.yaml
level=WARN msg="unable to find exact version; falling back to closest available version" chart=capone-rke2 requested="" selected=0.1.7
Error: INSTALLATION FAILED: failed to create resource: ONECluster.infrastructure.cluster.x-k8s.io "k8s-gpu-test" is invalid: spec.publicNetwork.floatingIP: Invalid value: "null": spec.publicNetwork.floatingIP in body must be of type string: "null"
oneadmin@llm-test-env:~$ helm version
version.BuildInfo{Version:"v4.0.1", GitCommit:"12500dd401faa7629f30ba5d5bff36287f3e94d3", GitTreeState:"clean", GoVersion:"go1.25.4", KubeClientVersion:"v1.34"}
With helm 3.0 the installation works perfectly:
oneadmin@llm-test-env:~$ helm install --kubeconfig ./kubeconfig_management.yaml k8s-gpu-test capone/capone-rke2 --values ./values.yaml
NAME: k8s-gpu-test
LAST DEPLOYED: Thu Dec 11 10:55:22 2025
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
oneadmin@llm-test-env:~$ helm version
version.BuildInfo{Version:"v3.19.3", GitCommit:"0707f566a3f4ced24009ef14d67fe0ce69db4be9", GitTreeState:"clean", GoVersion:"go1.24.10"}
Needs further investigation
When some fields like CONTROL_PLANE_HOST are set to null or emtpy, the helm 4.0 chart installation returns the following error:
With helm 3.0 the installation works perfectly:
Needs further investigation