kubernetes-sigs/cluster-api

Decide a migration path for deprecated certManagerVersionAnnotation

Open

#9,145 opened on Aug 8, 2023

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Go (1,532 forks)auto 404
area/clusterctlhelp wantedkind/bugpriority/important-longtermtriage/accepted

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

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

Contributor guide

Research direction
Investigate the usage of certManagerVersionAnnotation in the codebase, understand the upgrade path from v1alpha3 to current, and propose a migration plan that ensures backward compatibility while allowing removal of the deprecated annotation. Consider writing a migration controller or update logic to handle existing clusters.
Tech stack
go
Domain
backendinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoKubernetescluster api
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40