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
{{ message }}
Repository navigation
Improved out of the box SecondaryToPrimary mapping for KubernetesDependentResource. #1165
changed the title [-]`KubernetesDependentResource` should log warning if owner reference not added but `PrimaryToSecondaryMapper` is not implemented[/-][+]`KubernetesDependentResource` should log warning if owner reference not added but `SecondaryToPrimaryMapper` is not implemented[/+]on Apr 19, 2022
Discussed this on weekly, we could also approach this problem in a different way. That Kubernetes dependent resource might support in addition to owner reference handling also adding labels if the owner reference cannot be added (resources are in different namespace).
Basically with these two different approaches we cover every case. So should be supported out of the box. But also there should be a possibility for a custom approach.
changed the title [-]`KubernetesDependentResource` should log warning if owner reference not added but `SecondaryToPrimaryMapper` is not implemented[/-][+]Improved out of the box `SecondaryToPrimary` mapping for `KubernetesDependentResource`.[/+]on Apr 22, 2022
Activity
[-]`KubernetesDependentResource` should log warning if owner reference not added but `PrimaryToSecondaryMapper` is not implemented[/-][+]`KubernetesDependentResource` should log warning if owner reference not added but `SecondaryToPrimaryMapper` is not implemented[/+]csviri commentedon Apr 22, 2022
Discussed this on weekly, we could also approach this problem in a different way. That Kubernetes dependent resource might support in addition to owner reference handling also adding labels if the owner reference cannot be added (resources are in different namespace).
Basically with these two different approaches we cover every case. So should be supported out of the box. But also there should be a possibility for a custom approach.
[-]`KubernetesDependentResource` should log warning if owner reference not added but `SecondaryToPrimaryMapper` is not implemented[/-][+]Improved out of the box `SecondaryToPrimary` mapping for `KubernetesDependentResource`.[/+]