diff --git a/kubernetes/customresourcedefinitions.gen.yaml b/kubernetes/customresourcedefinitions.gen.yaml index 74be765fc5..9349214daa 100644 --- a/kubernetes/customresourcedefinitions.gen.yaml +++ b/kubernetes/customresourcedefinitions.gen.yaml @@ -10704,7 +10704,7 @@ spec: properties: bytes: description: response body as base64 encoded bytes. - format: binary + format: byte type: string string: type: string @@ -11756,7 +11756,7 @@ spec: properties: bytes: description: response body as base64 encoded bytes. - format: binary + format: byte type: string string: type: string @@ -12808,7 +12808,7 @@ spec: properties: bytes: description: response body as base64 encoded bytes. - format: binary + format: byte type: string string: type: string diff --git a/releasenotes/notes/58461.yaml b/releasenotes/notes/58461.yaml new file mode 100644 index 0000000000..75ed91df89 --- /dev/null +++ b/releasenotes/notes/58461.yaml @@ -0,0 +1,9 @@ +apiVersion: release-notes/v2 +kind: bug-fix +area: installation +issue: + - https://github.com/istio/istio/issues/58461 + +releaseNotes: + - | + **Fixed** warning when installing VirtualService CRD due to 'unrecognized format "binary"' by switching to `format: byte` for the field `spec.http.directResponse.body.bytes`. This does not impact user experience, as input is still expected in base64-encoded form as is already documented.