Pass Template object through to generated systemd unit values

[glitchcrab]

What does this PR do?

Passes the root Template object into the generated dictionary used to template the systemd additionalFields value out.

What is the effect of this change to users?

None, this is required to pass CI tests (ABS chart linting)

How does it look like?

N/A

Any background context you can provide?

Provider charts template out successfully locally, however when the chart linting steps are carried out in CI (on the provider chart), they fail with the following error:

[ERROR] templates/: template: cluster-cloud-director/charts/cluster/templates/clusterapi/workers/machinedeployment.yaml:38:79: executing "cluster-cloud-director/charts/cluster/templates/clusterapi/workers/machinedeployment.yaml" at <include "cluster.internal.workers.kubeadmConfig.spec.hash" $>: error calling include: template: cluster-cloud-director/charts/cluster/templates/clusterapi/workers/_helpers.tpl:2:12: executing "cluster.internal.workers.kubeadmConfig.spec.hash" at <include "cluster.internal.workers.kubeadmConfig.spec" $>: error calling include: template: cluster-cloud-director/charts/cluster/templates/clusterapi/workers/_helpers.tpl:8:6: executing "cluster.internal.workers.kubeadmConfig.spec" at <include "cluster.internal.workers.kubeadm.ignition" $>: error calling include: template: cluster-cloud-director/charts/cluster/templates/clusterapi/workers/_helpers_flatcar.tpl:8:10: executing "cluster.internal.workers.kubeadm.ignition" at <include "cluster.internal.workers.kubeadm.ignition.containerLinuxConfig.additionalConfig.systemd.units" $>: error calling include: template: cluster-cloud-director/charts/cluster/templates/clusterapi/workers/_helpers_flatcar.tpl:20:4: executing "cluster.internal.workers.kubeadm.ignition.containerLinuxConfig.additionalConfig.systemd.units" at <include "cluster.internal.kubeadm.ignition.containerLinuxConfig.additionalConfig.systemd.units" $systemdUnitValues>: error calling include: template: cluster-cloud-director/charts/cluster/templates/clusterapi/_helpers_flatcar.tpl:76:7: executing "cluster.internal.kubeadm.ignition.containerLinuxConfig.additionalConfig.systemd.units" at <tpl .contents.service.additionalFields $>: error calling tpl: cannot retrieve Template.Basepath from values inside tpl function: {{- if $.global.connectivity.network.staticRoutes }}
ExecStart=/usr/bin/bash -cv 'sleep 3'
{{- range $.global.connectivity.network.staticRoutes }}
ExecStart=/usr/bin/bash -cv 'ip route add {{ .destination }} via {{ .via }}'
{{- end }}
{{- end }}: "BasePath" is not a value

What is needed from the reviewers?

Do the docs need to be updated?

Should this change be mentioned in the release notes?

• CHANGELOG.md has been updated (if it exists)

[taylorbot]

Hey @glitchcrab, a test pull request has been created for you in the cluster-aws repo! Go to pull request giantswarm/cluster-aws#884 in order to test your cluster chart changes on AWS.

[github-actions]

There were no differences in the rendered Helm template.

Output

=== Differences when rendered with values file helm/cluster/ci/test-required-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster/ci/test-zot-mc-and-local-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster/ci/test-zot-mc-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster/ci/test-zot-only-local-values.yaml ===

No difference


=== No differences at all ===