Operators have reported that Konvoy fails to provision a cluster when extra spaces are present in the cluster.yaml. Specifically, the issue has been encountered when defining custom values for kubeaddons. This is an example of the output when this issue occurs:
STAGE [Verifying that nodes were provisioned] Error: failed to deploy the cluster: error provisioning cluster: unable to verify health of the provisioned nodes: unable to establish healthiness of the nodes: running ansible playbook failed: unable to copy "/tmp/cluster_config.toml510143865" to "/tmp/konvoy/konvoy_v1.8.0/runs/Verifying that nodes were provisioned/2021-06-29-19-29-57": yaml: line 77: found unknown escape character exit status 1
In this example output, we can see that konvoy is complaining about the formatting of our cluster.yaml. Although this output includes a reference to line 77 and mentions that an unknown escape is found, that’s not accurate and doesn't tell us exactly on which lines the extra spaces are.
If this issue is encountered, you should edit the cluster.yaml and remove the extra spaces. In the example below, there are 3 lines with extra spaces (“config:”, “Skip_Long_Lines On” and “Time Format”) under the fluentbit kube-addon stanza.
We recommend using a text editor capable of highlighting trailing spaces to inspect and edit the cluster.yaml.