Why resources in a Streams namespace have references to v1beta2 after a successful migration to v1

Issue

After migrating my Streams for Apache Kafka namespace from API version v1beta2 to API version v1 using the API conversion tool, I notice that several resources from the namespace
still hold a reference to the v1beta2, for example

apiVersion: v1
data:
  [ommited]
kind: Secret
metadata:
  annotations:
    strimzi.io/cluster-ca-cert-generation: "0"
  creationTimestamp: "2026-09-09T20:50:31Z"
  labels:
    app.kubernetes.io/instance: my-cluster2
    app.kubernetes.io/managed-by: strimzi-cluster-operator
    app.kubernetes.io/name: kafka
    app.kubernetes.io/part-of: strimzi-my-cluster2
    strimzi.io/cluster: my-cluster2
    strimzi.io/component-type: kafka
    strimzi.io/kind: Kafka
    strimzi.io/name: my-cluster2-kafka
  name: my-cluster2-dual-role-0
  namespace: namespace2
  ownerReferences:
  - apiVersion: kafka.strimzi.io/v1beta2 #<------ REFERENCE
    blockOwnerDeletion: true
    controller: false
    kind: Kafka
    name: my-cluster2
    uid: 656df745-247f-49bb-a4a8-af69e8ebb465
  resourceVersion: "5265962"
  uid: c3a4bdd2-25b8-4c87-b9eb-2387b2ece6e2
type: Opaque