Getting below error while doing pre-flight check

Hello Colleagues,

Getting below error while doing pre-flight checks :

[nutanix@backup-test-4b37b1-master-0 ~]$ helm search repo k10

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/nutanix/.kube/config

WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/nutanix/.kube/config

NAME             CHART VERSION APP VERSION DESCRIPTION                                 

kasten/k10       6.5.4        6.5.4      Kasten’s K10 Data Management Platform       

kasten/k10restore 6.5.4        6.5.4      A Helm chart for restoring K10 from a backup

[nutanix@backup-test-4b37b1-master-0 ~]$ 

[nutanix@backup-test-4b37b1-master-0 ~]$ curl https://docs.kasten.io/tools/k10_primer.sh | bash

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100 10828  100 10828    0     0  41630      0 --:--:-- --:--:-- --:--:-- 41806

Namespace option not provided, using default namespace

Checking for tools

 --> Found kubectl

 --> Found helm

 --> Found jq

 --> Found cat

 --> Found base64

 --> Found tr

Checking if the Kasten Helm repo is present

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/nutanix/.kube/config

WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/nutanix/.kube/config

 --> The Kasten Helm repo was found

Checking for required Helm version (>= v3.10.0)

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/nutanix/.kube/config

WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/nutanix/.kube/config

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/nutanix/.kube/config

WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/nutanix/.kube/config

 --> No Tiller needed with Helm v3.7.0

K10Primer image

 --> K10 version derived from the Helm repo () does not meet the minimum requirements (5.5.2)

Checking access to the Kubernetes context kubectl-context

 --> Able to access the default Kubernetes namespace

K10 Kanister tools image

 --> K10 version derived from the Helm repo () does not meet the minimum requirements (5.5.2)

Preflight checks failed

[nutanix@backup-test-4b37b1-master-0 ~]$ 

Tried below command as well : but same error 

[nutanix@backup-test-4b37b1-master-0 ~]$ curl -s https://docs.kasten.io/tools/k10_primer.sh  | bash /dev/stdin  -i gcr.io/kasten-images/k10tools:6.5.3

Namespace option not provided, using default namespace

Checking for tools

 --> Found kubectl

 --> Found helm

 --> Found jq

 --> Found cat

 --> Found base64

 --> Found tr

Checking if the Kasten Helm repo is present

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/nutanix/.kube/config

WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/nutanix/.kube/config

 --> The Kasten Helm repo was found

Checking for required Helm version (>= v3.10.0)

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/nutanix/.kube/config

WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/nutanix/.kube/config

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/nutanix/.kube/config

WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/nutanix/.kube/config

 --> No Tiller needed with Helm v3.7.0

K10Primer image

 --> Using Image (gcr.io/kasten-images/k10tools:6.5.3) to run test

Checking access to the Kubernetes context kubectl-context

 --> Able to access the default Kubernetes namespace

K10 Kanister tools image

 --> K10 version derived from the Helm repo () does not meet the minimum requirements (5.5.2)

Preflight checks failed

[nutanix@backup-test-4b37b1-master-0 ~]$ 

Kindly check and assist if somebody knows how to resolve this issue.