-
Bug
-
Resolution: Done
-
Blocker
-
1.32.0, 1.31.1
-
None
-
None
-
False
-
None
-
False
-
-
On an OCP 4.15.0 cluster, I am seeing a continuous modification of the knative-serving config-service-ca-trusted-ca ConfigMap that seems to cause quite a lot of traffic for configmap watchers. it seems the serverless operator is fighting with the cluster-network-operator, which tries to add the openshift.io/owning-component annotation, which the SO operator then tries to clear, which causes an endless loop of both operators trying to reconcile the CM
kind: ConfigMap
metadata:
annotations:
openshift.io/owning-component: Networking / cluster-network-operator
creationTimestamp: "2024-03-05T08:39:03Z"
labels:
config.openshift.io/inject-trusted-cabundle: "true"
managedFields:
- apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:data:
f:ca-bundle.crt: {}
f:metadata:
f:annotations:
f:openshift.io/owning-component: {}
manager: cluster-network-operator/configmap_ca
operation: Apply
time: "2024-03-05T09:55:18Z"
