kubernetes-sigs/cluster-api

Clusterctl move must surface object not included in the move sequence

Open

#8,387 opened on Mar 27, 2023

View on GitHub
 (7 comments) (0 reactions) (1 assignee)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?

See the discussion in https://github.com/kubernetes-sigs/cluster-api/issues/8384, and most specifically https://github.com/kubernetes-sigs/cluster-api/issues/8384#issuecomment-1485726840.

TL;DR; try to move an object when one of its parents is not being moved

What did you expect to happen?

Clusterctl move must surface object not included in the move sequence and why

Cluster API version

1.4.0 rc1 (and older versions)

Kubernetes version

No response

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug /area clusterctl

Contributor guide

Research direction
Investigate the clusterctl move logic to identify where objects are omitted from the move sequence and ensure they are surfaced with the reason for exclusion.
Tech stack
go
Domain
backenddevops
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.
Half day
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.
Needs investigation
Prerequisites
GoKubernetesCluster API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30