Add --name-template flag for generate cluster sub-command

[rbjorklin]

What would you like to be added (User Story)?

1. As an operator I would like to be able to exclude the cluster name from the name of all the generated resources. Given that all resources are namespaced the value of having the name also included in each resource name eludes me.

Detailed Description

I would like to be able to call clusterctl generate cluster --name-template '{{ .Name }}' and have that exclude the cluster name from each individual resource. The current default could be considered to be of the form: {{ .ClusterName }}-{{ .Name }}

Anything else you would like to add?

This idea is not new, helm has this feature. See helm/helm#1015

Label(s) to be applied

/kind feature

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fabriziopandini]

Let's see if other users have similar needs, but IMO we should not compare clusterctl to full-fledged template engines, and thus also assume advanced template features should be considered out of scope.

The core scope of clusterctl is to provide a solution to manage the lifecycle of providers - which is a complex and very specific problem - while managing templates is a facility we provided to get users started, but we are well aware that the majority of users rely on other tools existing in the ecosystem which are great in managing yaml, like helm, kapp or git-ops tools.

Also, clusterctl already supports pluggable template engines, so if someone wants more advanced templating features this can be achieved by using clusterctl as a library and providing a type that implements this interface.

There are also "no code" options, like https://cluster-api.sigs.k8s.io/clusterctl/configuration.html#provider-repositories or https://cluster-api.sigs.k8s.io/clusterctl/configuration.html#overrides-layer.

Last but not least, I would prefer to not add more complexity to our yaml processor before we define a path forward for #8325

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[rbjorklin]

assume advanced template features should be considered out of scope.

Fair enough.