Hm. I think we have a few options:

• Delete the entire log statement
• Delete only the source k/v pair
• Use %T as value for the source k/v pair (not sure how useful this information is though)

(cc @alvaroaleman)

Delete only the source k/v pair

I vote for this.

Weird, did we break this or did it never work but no one reported it?

I think we didn't break it, it's just that not every source is nicely printable that way :)

E.g. kind source looks better:

{"ts":1723448825525.443,"caller":"controller/controller.go:173","msg":"Starting EventSource","controller":"remote/clustercache","controllerGroup":"cluster.x-k8s.io","controllerKind":"Cluster","v":0,"source":"kind source: *v1beta1.Cluster"}

Hm, I guess actually the better fix would be to add String() funcs to the sources that don't have one already

@tamalsaha What source are you using?

func(event.TypedCreateEvent[sigs.k8s.io/controller-runtime/pkg/client.Object]) bool

Is this a builtin source from controller-runtime or one that has been implemented outside of it?

This is a typical SetupWithManager() method written in our operator. It is coming from one of these 2 Setups:

• https://github.com/open-viz/grafana-tools/blob/master/pkg/controllers/servicemonitor/federation_controller.go#L514C32-L529
• https://github.com/open-viz/grafana-tools/blob/master/pkg/controllers/servicemonitor/auto_controller.go#L215-L227

Hm that's strange. I would have expected all of them to use the kind source and thus have a String() func and produce a similar output to: #2914 (comment)

I'm wondering what logger is used that tries to convert the source to a JSON.

We're using component-base in Cluster API and neither the text format (klog) nor the JSON format (zap) is doing this:

text:

I0812 12:40:03.514514 17 controller.go:173] "Starting EventSource" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" source="kind source: *v1beta1.ClusterClass"

JSON:

{"ts":1723448825525.5396,"caller":"controller/controller.go:173","msg":"Starting EventSource","controller":"clusterclass","controllerGroup":"cluster.x-k8s.io","controllerKind":"ClusterClass","v":0,"source":"kind source: *v1beta1.ClusterClass"}

"k8s.io/klog/v2/klogr" klogr.New()

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten