<p>According to the <a href="https://github.com/operator-framework/operator-sdk/blob/f61941daa4685e9bd072d932788accfd73372d05/doc/design/long-term/norms-to-follow.md" rel="nofollow noreferrer">operator-sdk doc</a>
This is a common mistake made by operator developers.</p>
<blockquote>
<p>Methods for connecting Kubernetes objects through labels, OwnerRefs, status etc that may be incompatible with future updates or too restrictive in the long term.</p>
</blockquote>
<p>What is the right way then?
How to connect related objects whithout <code>labels</code> and <code>OwnerRefs</code>?</p>

<p>That document is likely going to be removed soon, there's a maintained best practices document here: <a href="https://github.com/operator-framework/community-operators/blob/master/docs/best-practices.md" rel="nofollow noreferrer">https://github.com/operator-framework/community-operators/blob/master/docs/best-practices.md</a></p>

<p>Using labels and ownerRefs is a good way to connect related resources (we even enforce ownerRefs for Ansible-based Operators), so I would ignore that guidance.</p>
