From 6b04cd9afedb23c52ebffc15623ce49ae82ea8ae Mon Sep 17 00:00:00 2001 From: Erik Godding Boye Date: Tue, 26 Nov 2024 20:33:33 +0100 Subject: [PATCH] Add more about spec/status in tech controller Signed-off-by: Erik Godding Boye --- design/20241124-rename-bunde-to-clusterbundle.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/design/20241124-rename-bunde-to-clusterbundle.md b/design/20241124-rename-bunde-to-clusterbundle.md index 8c864e11..c2c93a6b 100644 --- a/design/20241124-rename-bunde-to-clusterbundle.md +++ b/design/20241124-rename-bunde-to-clusterbundle.md @@ -104,7 +104,10 @@ When the functional controller is migrated to target `ClusterBundle`, we want to controller targeting the now deprecated `Bundle` resource. This controller should just create or update the `ClusterBundle` with the same name as the reconciled `Bundle`. -Since the APIs should have identical `spec`, this should be a simple controller. +Since the APIs should be quite similar, this should be a simple controller. + +- `Bundle` `.spec` should be copied (and eventually slightly converted) into `ClusterBundle` `.spec` +- `Bundle` `.status` should be updated from `ClusterBundle` `.status` To allow a user to migrate their resources from `Bundle` to `ClusterBundle`, the controller should not act on `Bundle` delete events - nor should it add an owner reference to `ClusterBundle` to avoid the Kubernetes garbage collector