You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#259 introduced a new way to link ControlPlane's cluster wide resources to the managing ControlPlane via labels.
This approach works but it misses the migration approach:
users install ControlPlanes using KGO 1.2 (or older)
KGO creates owner reference bindings between ControlPlane's cluster wide resources to the managing ControlPlane
users upgrade KGO to 1.3
KGO looks up the cluster wide resources via the new, label based approach, and misses the old ones that are already created, and thus tries to create the already existing resources
Since we're using the new label set for both the generation and existing resources lookup, existing objects (created with old labels set) are not matched and hence a create operation is performed which should be an update to migrate to the new set of labels.
Acceptance criteria
When KGO is upgraded from 1.2 to 1.3 ControlPlane managed cluster wide resources have their labels properly migrated (updated) and are properly looked up
Problem statement
#259 introduced a new way to link
ControlPlane
's cluster wide resources to the managingControlPlane
via labels.This approach works but it misses the migration approach:
ControlPlane
s using KGO 1.2 (or older)ControlPlane
's cluster wide resources to the managingControlPlane
Logs:
This causes e2e upgrade tests to fail.
Steps to reproduce:
Gateway
does not getProgrammed
Anything else ?
Old labels
New labels
Since we're using the new label set for both the generation and existing resources lookup, existing objects (created with old labels set) are not matched and hence a create operation is performed which should be an update to migrate to the new set of labels.
Acceptance criteria
ControlPlane
managed cluster wide resources have their labels properly migrated (updated) and are properly looked upThe text was updated successfully, but these errors were encountered: