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
Age after which orphan sstables can be deleted from the storage backend. Protects from race conditions between purge and ongoing backups. Defaults to 10 days.
false
bucketName
string
The name of the bucket to use for the backups.
false
concurrentTransfers
integer
Number of concurrent uploads. Helps maximizing the speed of uploads but puts more pressure on the network. Defaults to 1.Default: 1
false
host
string
Host to connect to for the storage backend.
false
maxBackupAge
integer
Maximum backup age that the purge process should observe.Default: 0
false
maxBackupCount
integer
Maximum number of backups to keep (used by the purge process). Default is unlimited.Default: 0
false
multiPartUploadThreshold
integer
File size over which cloud specific cli tools are used for transfer. Defaults to 100 MB.Default: 104857600
false
port
integer
Port to connect to for the storage backend.
false
prefix
string
Name of the top level folder in the backup bucket. If empty, the cluster name will be used.
false
region
string
Region of the storage bucket. Defaults to "default".
false
secure
boolean
Whether to use SSL for the storage backend.
false
storageProvider
enum
The storage backend to use for the backups.Enum: local, google_storage, azure_blobs, s3, s3_compatible, s3_rgw, ibm_storage
false
storageSecretRef
string
Kubernetes Secret that stores the key file for the storage provider's API. If using 'local' storage, this value is ignored.
false
transferMaxBandwidth
string
Max upload bandwidth in MB/s. Defaults to 50 MB/s.Default: 50MB/s
false
Initially, the controller for this API would only verify that the referenced secret is available and update the status accordingly.
In the future it could attempt a connection to the bucket and update the status of the object to indicate if the settings are valid and allow a successful connection.
The referenced secret must exist in the same namespace as the MedusaConfiguration object.
The content you are editing has changed. Please copy your edits and refresh the page.
The MedusaConfiguration API schema will use the same type as Medusa's storage properties.
Initially, the controller for this API would only verify that the referenced secret is available and update the status accordingly.
In the future it could attempt a connection to the bucket and update the status of the object to indicate if the settings are valid and allow a successful connection.
The referenced secret must exist in the same namespace as the MedusaConfiguration object.
Definition of Done
The text was updated successfully, but these errors were encountered: