Merge pull request #7332 from blackpiglet/update_document

Modify S3ForcePathStyle description.
pull/7334/head
Shubham Pampattiwar 2024-01-18 10:00:27 -08:00 committed by GitHub
commit c9b1f1c23e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 15 additions and 14 deletions

View File

@ -87,7 +87,7 @@ These instructions start the Velero server and a Minio instance that is accessib
* This example also assumes you have named your Minio bucket "velero".
* Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will cause Velero can upload data to MinIO, but cannot download from MinIO. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue.
* Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue.
It can be resolved by two ways:
* Set `s3ForcePathStyle=true` for parameter `--backup-location-config` when installing Velero. This is the preferred way.
* Make MinIO server support virtual-host style address. Add the [MINIO_DOMAIN environment variable](https://min.io/docs/minio/linux/reference/minio-server/settings/core.html#id5) for MinIO server will do the magic.

View File

@ -87,7 +87,7 @@ These instructions start the Velero server and a Minio instance that is accessib
* This example also assumes you have named your Minio bucket "velero".
* Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will cause Velero can upload data to MinIO, but cannot download from MinIO. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue.
* Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue.
It can be resolved by two ways:
* Set `s3ForcePathStyle=true` for parameter `--backup-location-config` when installing Velero. This is the preferred way.
* Make MinIO server support virtual-host style address. Add the [MINIO_DOMAIN environment variable](https://min.io/docs/minio/linux/reference/minio-server/settings/core.html#id5) for MinIO server will do the magic.

View File

@ -1,14 +1,15 @@
{{ $versions := site.Params.versions }}
{{ $latest := site.Params.latest }}
/docs /docs/{{ $latest }} 301!
/docs/latest /docs/{{ $latest }}
/docs/latest/* /docs/{{ $latest }}/:splat
/docs/troubleshooting /docs/{{ $latest }}/troubleshooting
/docs/supported-providers /docs/{{ $latest }}/supported-providers
/docs/zenhub /docs/{{ $latest }}/support-process
/docs/install-overview /docs/{{ $latest }}/basic-install
/docs/start-contributing /docs/{{ $latest }}/start-contributing
/docs/customize-installation /docs/{{ $latest }}/customize-installation
/docs/faq /docs/{{ $latest }}/faq
/docs/csi /docs/{{ $latest }}/csi
/docs/file-system-backup /docs/{{ $latest }}/file-system-backup
/docs /docs/{{ $latest }} 301!
/docs/latest /docs/{{ $latest }}
/docs/latest/* /docs/{{ $latest }}/:splat
/docs/troubleshooting /docs/{{ $latest }}/troubleshooting
/docs/supported-providers /docs/{{ $latest }}/supported-providers
/docs/zenhub /docs/{{ $latest }}/support-process
/docs/install-overview /docs/{{ $latest }}/basic-install
/docs/start-contributing /docs/{{ $latest }}/start-contributing
/docs/customize-installation /docs/{{ $latest }}/customize-installation
/docs/faq /docs/{{ $latest }}/faq
/docs/csi /docs/{{ $latest }}/csi
/docs/file-system-backup /docs/{{ $latest }}/file-system-backup
/docs/csi-snapshot-data-movement /docs/{{ $latest }}/csi-snapshot-data-movement