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.
In the 0.2.22 release of Tator, support for OCI Object Storage as a bucket was added. This required
a refactor of how bucket configurations are stored by Tator, which is not backwards compatible. The
0.2.22 release deprecates the existing method of creating and updating buckets, but still allows for
buckets created this way to function. Release 1.0.0 will deprecate the functionality of buckets
created this way, but there is a utility that will assist your migration from the old configuration
to the new one.