Skip to content

Handling Cluster Scoped Primary Resource in Dependent Resource SecondaryToPrimaryMapper  #2311

@csviri

Description

@csviri

Currently by default Dependent Resource assumes that the primary resource is namespace scoped, see:

This is something users have to then handle explicitly, by overriding the SecondaryToPrimaryMapper, see:

#2310 (comment)

In DRs we don't have access to the class of primary to check if it is namespace scoped. But we might create some workarounds, like passing it as a flag for managed resources automatically.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions