Converting Bucket Configurations for Tator 1.0.0

What changed

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 values.yaml:

• objectStorageHost is now liveBucket and it is an object containing the config settings instead of just the hostname of the store

• All three of uploadBucket, liveBucket, and backupBucket share the following structure:

  <role>Bucket:
    config: "json in folded block (>- ...)"
    storeType: "<one of AWS, MINIO, GCP, or OCI>"
    name: "<your bucket name>"

• The bucket definition in the minio section needs to be updated by adding the above three key-value pairs, like so:

  minio:
    enabled: true
    accessKey: AKIAIOSFODNN7EXAMPLE
    secretKey: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
    config: >-
      {
        "aws_access_key_id": "AKIAIOSFODNN7EXAMPLE",
        "aws_secret_access_key": "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY",
        "endpoint_url": "http://tator-minio:9000",
        "region_name": "us-east-2"
      }
    name: tator
    store_type: "MINIO"
    persistence:
      size: "1Ti"
      existingClaim: "main-pv-claim"
      subPath: "objects"
    defaultBucket:
      enabled: true
      name: tator

  accessKey and secretKey are required by the dependent minio helm chart and should match the aws_access_key_id and aws_secret_access_key, respectively.