Clarify support for S3 compatible services in container registry
What does this MR do?
Among others, the container registry supports S3 as the blob storage backend. In the last years, there has been a significant increase in so-called S3 compatible services, which reportedly implement APIs fully compliant with the AWS S3 specification.
Recently we have seen an increase in the container registry issues that are related to the use of such S3 compatible services, such as radosgw. Although most of the time we're able to help users and provide workarounds, we must not patch the registry unless the issue is reproducible against the reference S3 implementation from AWS.
This MR proposes the addition of a note to the container registry documentation, saying that we cannot guarantee support for S3 compatible services, neither we intend to patch the registry unless an issue is reproducible against AWS S3.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team