Add namingStrategy for InfrastructureCluster

[simonostendorf]

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

As a cluster administrator I want to control how my InfrastructureClusters are named so that they match my other cluster-api components.

Detailed Description

When using cluster-classes the user can change the naming scheme of the resulting control-plane and the machine-deployment / machine-pool objects but not for the infrastructure cluster.

I think it would be nice to support a namingStrategy for infrastructure as well. This would allow me to remove the random id at the end because my cluster names are already random ids.

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature

/area cluster-class

[k8s-ci-robot]

@simonostendorf: The label(s) area/cluster-class cannot be applied, because the repository doesn't have them.

In response to this:

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

As a cluster administrator I want to control how my InfrastructureClusters are named so that they match my other cluster-api components.

Detailed Description

When using cluster-classes the user can change the naming scheme of the resulting control-plane and the machine-deployment / machine-pool objects but not for the infrastructure cluster.

I think it would be nice to support a namingStrategy for infrastructure as well. This would allow me to remove the random id at the end because my cluster names are already random ids.

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature

/area cluster-class

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-sigs/prow repository.

[simonostendorf]

/area clusterclass

[chrischdi]

/triage accepted
/priority backlog

Feel free to take a look, assign and open a PR for this :-)

[chrischdi]

/help

[k8s-ci-robot]

@chrischdi:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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-sigs/prow repository.

[arshadd-b]

/assign