Closed akutz closed 4 years ago
/kind bug
What steps did you take and what happened: Because the kubeadm bootstrapper is encoding any additional files as base64 (https://github.com/kubernetes-sigs/cluster-api-bootstrap-provider-kubeadm/blob/e3b2bcf70c84fed5ca2e0030e5b96fef6ee6aa83/cloudinit/files.go#L31), the contents of the files are not getting interpolated with the cloud-init instance data, and thus we get files like this:
root@v1a2:~# cat /etc/hostname {{ ds.meta_data.hostname }}
root@v1a2:~# cat /etc/hosts ::1 ipv6-localhost ipv6-loopback 127.0.0.1 localhost 127.0.0.1 {{ ds.meta_data.hostname }}
Files shouldn’t be automatically encoded to base64 unless requested.
What did you expect to happen: Unless part of the encoding type, a file's contents should not be automatically encoded as base64.
/assign @chuckha /lifecycle active /milestone v0.1
Closed by #204
/kind bug
What steps did you take and what happened: Because the kubeadm bootstrapper is encoding any additional files as base64 (https://github.com/kubernetes-sigs/cluster-api-bootstrap-provider-kubeadm/blob/e3b2bcf70c84fed5ca2e0030e5b96fef6ee6aa83/cloudinit/files.go#L31), the contents of the files are not getting interpolated with the cloud-init instance data, and thus we get files like this:
Files shouldn’t be automatically encoded to base64 unless requested.
What did you expect to happen: Unless part of the encoding type, a file's contents should not be automatically encoded as base64.