auto-owner-reference setter

[DirectXMan12]

We might want to consider a mode or something that automatically sets owner references. It's not clear exactly what that looks like (client option? wrapping client?), but it's something to think about.

/kind feature

[shawn-hurley]

I really like this idea.

We need to make sure that we do the correct thing and make sure that namespaced resources are not owners of cluster scoped resources. I think how we want to handle this scenario either error out or hide this complexity will determine the best design. For instance, if we tried to hide the complexity, then a wrapping client would make the most sense to me because everything that can get the owner ref should. If we want to error out, I think the client options is the best, so a user has to add it to the correct resources themselves.

WDYT?

[DirectXMan12]

well, client option is "easy" in that we can always build the wrapping client on top of it

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[DirectXMan12]

/lifecycle frozen

[vincepri]

/kind design
/milestone Next

[vincepri]

/priority backlog

[vincepri]

Closing this as setting owner references should be easy enough within reconciler code

/close