Owner references are not correctly resolved when primary resource has empty group

[mnk]

Bug Report

What did you do?

When implementing a workflow where the primary resource is a standard K8s kind (ConfigMap)
I was unable to get the secondary resources from the context.

What did you expect to see?

I expected to be able to fetch the secondary resources via context.getSecondaryResource

What did you see instead? Under which circumstances?

The secondary resources are always null

Environment

Running latest from main branch 5.0.4-SNAPSHOT

Possible Solution

The problem seems to be caused by a bug in the apiVersion matching. I will post a fix proposal as PR.

[mnk]

Temporary workaround merged to java-operator-sdk and fix for root cause also merged to kubernetes-client