In the 1.0.0 release of Tator, the fields related to default upload, live, and backup buckets in the
values.yaml configuration file have changed to match the changes from the 0.2.22 release. This is
a breaking change and your tator deployment will be broken if your deployment administrator does not
follow these instructions during the upgrade to 1.0.0.
How to update a deployment's default buckets
Updating the default upload, live, and backup buckets is a manual process. The following changes
have been made to
liveBucketand it is an object containing the config settings instead of just the hostname of the store
All three of
backupBucketshare the following structure:
config: "json in folded block (>- ...)"
storeType: "<one of AWS, MINIO, GCP, or OCI>"
name: "<your bucket name>"
The bucket definition in the
miniosection needs to be updated by adding the above three key-value pairs, like so:
secretKeyare required by the dependent minio helm chart and should match the