Safe production upgrade from Jaeger Operator 1.62.0 to 1.65.0

[am36166]

Hello,

I am planning to upgrade Jaeger Operator in production from 1.62.0 to 1.65.0.

I compared the official manifests. The only difference is:

-jaeger-operator:1.62.0
+jaeger-operator:1.65.0

The Jaeger CRDs are byte-for-byte identical and both use:

name: v1
served: true
storage: true

My plan is to:

Back up the operator Deployment and existing Jaeger resources.
Record or pin the current Jaeger component images.
Upgrade only the operator image.
Verify reconciliation, ingestion, query, and storage.
Roll back to 1.62.0 if issues occur.

Could you please confirm:

Is this in-place upgrade supported?
Will the new operator automatically handle existing Jaeger resources?
Can managed Jaeger workloads be upgraded automatically if images are not pinned?
Is restoring the operator image to 1.62.0 a safe rollback approach?
Are there any known breaking or behavioral changes between these versions?

Environment:
Kubernetes V1.34.1

Thank you.