Open coltmcnealy-lh opened 4 hours ago
I need to double check but isn't the type of the primary known when the annotations are used?
Indeed, the owner type is not known. However, this will require deeper changes than simply adding the annotation because the mappers only return ResourceID
instances, which, currently, only also record name and namespaces.
@metacosm I'm pretty sure we don't need to extend resourceID, note that from v5 we do type checking for owner references, adding type annotation should do the trick, and have the secondary filter on the.
Another option is just use labels/ label selectors, which is also more efficient.
Or both.
I have a reconciler that extends
KubernetesCRUDNoGCDependentResource
. The created dependent has the following annotations:In my operator, I have several different
CustomResourceDefinition
s and reconcilers. Therefore, I can and do have multiple custom resources in themy-namespace
namespace calledmy-thing
.In my own code, I need to determine the owner of these resources. I can solve that by putting labels/annotations on them myself (this is quite a bit of work). However, I imagine that this is likely a vulnerability to bugs.
Proposed Solution
Add another annotation to
NoGC
resources and use that for determining ownership: