kubernetes-sigs/cluster-api

Decide a migration path for deprecated certManagerVersionAnnotation

開放

#9,145 建立於 2023年8月8日

 (7 則留言) (0 個反應) (0 位負責人)Go (1,532 個分叉)auto 404
area/clusterctlhelp wantedkind/bugpriority/important-longtermtriage/accepted

倉庫指標

星標
 (4,267 顆星)
PR 合併指標
 (PR 指標待抓取)

描述

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 https://github.com/kubernetes-sigs/cluster-api/pull/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: https://github.com/kubernetes-sigs/cluster-api/pull/9136#discussion_r1286060493

Label(s) to be applied

/kind bug /area clusterctl

貢獻者指南