Skip to main content

5 posts tagged with "upgrade"

View All Tags

· One min read
Jonathan Takahashi

This blog post will go over the procedure for migrating a Tator deployment based on Kubernetes (pre-1.1.0) to Docker Compose (1.1.0 and later). Because all dependencies use the same Docker images as version 1.0.0, this migration procedure is fairly simple and consists of simply pointing the new compose deployment to the directory that was previously in use.

· 4 min read
Jonathan Takahashi

This blog post will go over the procedure for upgrading a Tator deployment to the upcoming major release, 1.0.0, with most features recently merged with the main branch. This release requires an upgrade to Postgresql 14 and drops the Elasticsearch dependency for standard queries (although it is still used for storing logs). Deprecated bucket definition formats are also removed in this release. This post assumes that the tator deployment is currently running version 0.2.23, was installed with the install script, and is running on microk8s.

· 2 min read
Hugh Enxing

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.

· One min read
Hugh Enxing

What changed​

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.

· 5 min read
Hugh Enxing

This blog post will go over the procedure for upgrading a Tator deployment to the latest release, 0.2.19. This release updates the versions of some dependencies, which require more user actions than the standard upgrade process. It assumes that the tator deployment was set up using the install script and is running on microk8s.