Decide a migration path for deprecated certManagerVersionAnnotation

[furkatgofurov7]

What steps did you take and what happened?

We have a certManagerVersionAnnotation = "certmanager.clusterctl.cluster.x-k8s.io/version annotation which is maintained only for supporting upgrades from clusters created with clusterctl v1alpha3. We are working towards removing a previously deprecated code in #9136 and this annotation might not be removed since there is no migration code for it and we have to keep it in order to support clusters created with this annotation.

What did you expect to happen?

We need to decide how we would provide a clear migration tasks for this specific annotation not to break clusters created with v1alpha3

Cluster API version

main

Kubernetes version

N/A

Anything else you would like to add?

See more the discussion here: #9136 (comment)

Label(s) to be applied

/kind bug
/area clusterctl

[furkatgofurov7]

/area clusterctl

/cc @killianmuldoon FYI

[killianmuldoon]

Thanks for opening this @furkatgofurov7

/assign

I'll take a look at figuring out the current state of this.

[furkatgofurov7]

/assign

I'll take a look at figuring out the current state of this.

@killianmuldoon thanks!

/triage accepted

[killianmuldoon]

/unassign

Not going to get to this for now.

[fabriziopandini]

/priority important-longterm

[fabriziopandini]

This needs someone to look into
/help

[k8s-ci-robot]

@fabriziopandini:
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:

This needs someone to look into
/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.