objectsearch bug report

[tangming1996]

What happened:
After the objectsearch resource is deleted, its associated pod resource remains
What you expected to happen:
After the objectsearch resource is deleted, its associated pod resource is also deleted
How to reproduce it (as minimally and precisely as possible):
Create an objectsearch resource. After the pod instance is created, delete the objectsearch resource and check whether the Pods are also deleted.
Anything else we need to know?:

Environment:
kubernetes version: 1.23.0
kubeedge version: 1.16.1
sedna version: 0.6.0

CloudSide Environment:

Hardware configuration

$ lscpu
# paste output here

OS

$ cat /etc/os-release
# paste output here

Kernel

$ uname -a
# paste output here

Others

EdgeSide Environment:

Hardware configuration

$ lscpu
# paste output here

OS

$ cat /etc/os-release
# paste output here

Kernel

$ uname -a
# paste output here

Others

[tangming1996]

The main problem is that the ownerReferences/0/kind field was misrepresented as Name when pod associated the upper objectsearch resource, which should actually be KindName

The bug has since been fixed. #443

[MooreZheng]

Is this issue fixed by #444 ?