You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NetApp replied that they were able to reproduce the error in a lab environment. They inspected the network traffic and determined that the issue is caused by "the minio client library in RKE2 having a bug where gzip streamed data is terminated prematurely". They say that RKE2 sets Accept-Encoding: gzip but that the header is not honored by AWS or MinIO and thus they send non-compressed data back to RKE2. NetApp say that this is why it works on AWS but not in StorageGRID, and that StorageGRID always honors the Accept-Encording header.
It looks like minio has their own default transport which disables compression to work around this issue. We don't observe that same behavior when setting up the transports that was pass in to minio - which we do so that we can configure TLS options. https://github.com/minio/minio-go/blob/v7.0.83/transport.go#L41-L64
We should disable compression in the http.Transport that we are passing to minio, as they do the same internally when constructing their default transports.
The text was updated successfully, but these errors were encountered:
From rancher/rke2#6285 (reply in thread)
It looks like minio has their own default transport which disables compression to work around this issue. We don't observe that same behavior when setting up the transports that was pass in to minio - which we do so that we can configure TLS options.
https://github.com/minio/minio-go/blob/v7.0.83/transport.go#L41-L64
We should disable compression in the http.Transport that we are passing to minio, as they do the same internally when constructing their default transports.
The text was updated successfully, but these errors were encountered: