红帽全球峰会此内容没有您所选择的语言版本。
Chapter 11. Overview of object storage endpoints
To ensure correct configuration of object storage in OpenShift AI, you must format endpoints correctly for the different types of object storage supported. These instructions are for formatting endpoints for Amazon S3, MinIO, or other S3-compatible storage solutions, minimizing configuration errors and ensuring compatibility.
Properly formatted endpoints enable connectivity and reduce the risk of misconfigurations. Use the appropriate endpoint format for your object storage type. Improper formatting might cause connection errors or restrict access to storage resources.
11.1. MinIO (On-Cluster)
For on-cluster MinIO instances, use a local endpoint URL format. Ensure the following when configuring MinIO endpoints:
-
Prefix the endpoint with
http://orhttps://depending on your MinIO security setup. - Include the cluster IP or hostname, followed by the port number if specified.
-
Use a port number if your MinIO instance requires one (default is typically
9000).
Example:
http://minio-cluster.local:9000Verify that the MinIO instance is accessible within the cluster by checking your cluster DNS settings and network configurations.
11.2. Amazon S3
When configuring endpoints for Amazon S3, use region-specific URLs. Amazon S3 endpoints generally follow this format:
-
Prefix the endpoint with
https://. -
Format as
<bucket-name>.s3.<region>.amazonaws.com, where<bucket-name>is the name of your S3 bucket, and<region>is the AWS region code (for example,us-west-1,eu-central-1).
Example:
https://my-bucket.s3.us-west-2.amazonaws.comFor improved security and compliance, ensure that your Amazon S3 bucket is in the correct region.
11.3. Other S3-Compatible Object Stores
For S3-compatible storage solutions other than Amazon S3, follow the specific endpoint format required by your provider. Generally, these endpoints include the following items:
-
The provider base URL, prefixed with
https://. - The bucket name and region parameters as specified by the provider.
- Review the documentation from your S3-compatible provider to confirm required endpoint formats.
-
Replace placeholder values like
<bucket-name>and<region>with your specific configuration details.
Incorrectly formatted endpoints for S3-compatible providers might lead to access denial. Always verify the format in your storage provider documentation to ensure compatibility.
11.4. Verification and Troubleshooting
After configuring endpoints, verify connectivity by performing a test upload or accessing the object storage directly through the OpenShift AI dashboard. For troubleshooting, check the following items:
- Network Accessibility: Confirm that the endpoint is reachable from your OpenShift AI cluster.
- Authentication: Ensure correct access credentials for each storage type.
- Endpoint Accuracy: Double-check the endpoint URL format for any typos or missing components.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}