kubernetes-sigs/cluster-api

Provide a Way to Opt Out of Resource Adoption

Open

#7,913 opened on Jan 12, 2023

View on GitHub
 (14 comments) (1 reaction) (0 assignees)Go (1,532 forks)auto 404
help wantedkind/featurepriority/backlogtriage/accepted

Repository metrics

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

Description

User Story

Say I deploy a cluster via Helm and ArgoCD. I then want to delete a MachineDeployment, its KuebadmConfigTemplate and OpenstackMachineTemplate. Problem is that while Argo detects it doesn't need to manage these anymore, because they are no longer generated by Helm, it doesn't actually delete them because CAPI has implicitly added owner references to the Cluster. Argo thinks that these resources have been implicitly created by controller-x, as per standard Deployment/StatefulSet/etc semantics, so doesn't touch them.

The way CAPI works essentially prevents deletion of MachineDeployments in this context and requires manual deletion, which is a pain in the butt.

Detailed Description

What I want is a way to opt out of this adoption, so that the provisioning application is in control of its lifecycle, not CAPI.

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

/kind feature

Contributor guide

Research direction
Investigate how Cluster API adds owner references to resources like MachineDeployments, KubeadmConfigTemplates, and OpenstackMachineTemplates. Identify the code path where adoption occurs and explore options for an opt out mechanism, such as a label or annotation that prevents owner reference injection. Consider implications for garbage collection and resource lifecycle.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 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