Further info: helm: # Use a custom location for the Helm chart. This can refer to any go-getter URL or # OCI registry based helm chart URL e.g. "oci://ghcr.io/fleetrepoci/guestbook". # This allows one to download charts from most any location. Also know that # go-getter URL supports adding a digest to validate the download. If repo # is set below this field is the name of the chart to lookup chart: teleport-cluster # A https URL to a Helm repo to download the chart from. It's typically easier # to just use

chart

field and refer to a tgz file. If repo is used the # value of

chart

will be used as the chart name to lookup in the Helm repository. repo: https://charts.releases.teleport.dev # A custom release name to deploy the chart as. If not specified a release name # will be generated. releaseName: teleport-cluster # The version of the chart or semver constraint of the chart to find. If a constraint # is specified it is evaluated each time git changes. # The version also determines which chart to download from OCI registries. version: 10.2.2 # Any values that should be placed in the

values.yaml

and passed to helm during # install. valuesFiles: - values.yaml # Override immutable resources. This could be dangerous. force: false # Set the Helm --atomic flag when upgrading atomic: false clusterName: prm Any help appreciated. Tia

Seems you miss the clusterName in values.yaml. Which is the content of your values.yaml file?

yes i did. i got confused by the same value that fleet uses. my apologies for this post. thank you for the help @quick-sandwich-76600