Object Storage Managed Component (PROJQUAY-932) #298
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: https://issues.redhat.com/browse/PROJQUAY-932
Changelog: Add managed storage using
ObjectBucketClaim
API and removelocalstorage
component completely.Docs: Operator requires the
ObjectBucketClaim
API to be present on the cluster in order to have managed object storage component (multiple providers exist other than RHOCS). Otherwise, you must markobjectstorage
component asmanaged: false
and provide the config values yourself.ObjectBucketClaims
Testing: TODO(alecmerdler)
Details:
Adds
objectstorage
managed component for registry blob storage. Declaring this required component will cause the Operator to provision a bucket using theObjectBucketClaim
API and direct Quay to use that as a registry storage backend.