Important: RKE add-on install is only supported up to Rancher v2.0.8
Please use the Rancher Helm chart to install Rancher on a Kubernetes cluster. For details, see the Kubernetes Install .
If you are currently using the RKE add-on install method, see Migrating from a Kubernetes Install with an RKE Add-on for details on how to move to using the helm chart.
To debug issues around this error, you will need to download the command-line tool
kubectl. See Install and Set Up kubectl how to download
kubectl for your platform.
When you have made changes to
rancher-cluster.yml, you will have to run
rke remove --config rancher-cluster.yml to clean the nodes, so it cannot conflict with previous configuration errors.
Failed to deploy addon execute job [rke-user-includes-addons]: Failed to get job complete status
Something is wrong in the addons definitions, you can run the following command to get the root cause in the logging of the job:
kubectl --kubeconfig kube_config_rancher-cluster.yml logs -l job-name=rke-user-addon-deploy-job -n kube-system
error: error converting YAML to JSON: yaml: line 9:
The structure of the addons definition in
rancher-cluster.yml is wrong. In the different resources specified in the addons section, there is a error in the structure of the YAML. The pointer
yaml line 9 references to the line number of the addon that is causing issues.
- Is each of the base64 encoded certificate string placed directly after the key, for example: `tls.crt: LS01...`, there should be no newline/space before, in between or after.
- Is the YAML properly formatted, each indentation should be 2 spaces as shown in the template files.
- Verify the integrity of your certificate by running this command `cat MyCertificate | base64 -d` on Linux, `cat MyCertificate | base64 -D` on Mac OS . If any error exists, the command output will tell you.
Error from server (BadRequest): error when creating "/etc/config/rke-user-addon.yaml": Secret in version "v1" cannot be handled as a Secret
The base64 string of one of the certificate strings is wrong. The log message will try to show you what part of the string is not recognized as valid base64.Things to check
- Check if the base64 string is valid by running one of the commands below:
echo BASE64_CRT | base64 -D
echo BASE64_CRT | base64 -d
certutil -decode FILENAME.base64 FILENAME.verify
The Ingress "cattle-ingress-http" is invalid: spec.rules.host: Invalid value: "IP": must be a DNS name, not an IP address
The host value can only contain a host name, as it is needed by the ingress controller to match the hostname and pass to the correct backend.