As of kubernetes version 1.34, the API server now returns warnings to clients that create CRDs containing `string` type fields which specify an unknown format. The `virtualservices.networking.istio.io` CRD contains at least one string type field with the format `"binary"`, which is not a known format in kubernetes, and as a result we are now seeing e2e test failures because OLM is reporting these warnings as alerts to the cluster.

Any offending fields in the `virtualservices.networking.istio.io` CRD should be fixed by setting their format to `"byte"`, which is a known format, instead of `"binary"`. OLM will continue to issue cluster alerts until this is fixed, which could block testing or upgrade efforts.

See here for a list of known types. Notably, this differs from the formats allowed in the OpenAPI spec according to this.

Here is the output from the warning:

Event(v1.ObjectReference{Kind:"InstallPlan", Namespace:"openshift-operators", Name:"install-vrgkn", UID:"ae3e94ff-1b17-4fcd-b1db-36c3a240cc85", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"257249", FieldPath:"status.plan[9]"}): type: 'Warning' reason: 'AppliedWithWarnings' 1 warning(s) generated during installation of operator "servicemeshoperator3.v3.1.0" (CustomResourceDefinition "virtualservices.networking.istio.io"): unrecognized format "binary"