Release 2024.44 — Unique AI Documentation

Release 2024.44

Release Date: October 30, 2024


Customer Managed Tenant Changes

Clients hosting their own Unique now find detailed upgrade guides in 2024.44 - Infrastructure & Configuration Release Notes 📣

Announcements

Features

Improvements

Bug fixes


Open Source Helm Charts

It was never Uniques idea to hide its helm charts ( What is that?). Due to its scaling and growing nature and the clients demands for the more elaborate deployment models (Customer Managed and On Premise) it was time to move the charts out of Uniques mono repository code base and open source them like any state-of-the-art software does. Head over to https://github.com/Unique-AG/helm-charts to see the charts. Note that the charts themselves did neither change their content nor their version, they were just migrated into the new repository. You can also find them on Artifact Hub where they have some basic documentation Unique will improve on over the next quarters.

Key changes

Only helm charts were made publicly available, not the container images as these are the Enterprise Software under license.

Upgrade guide

These two pseudo pipelines show, how clients can adapt their infrastructure to leverage the new charts.

Before

docker login somecr.azurecr.io

Then in some files

chart: somecr.azurecr.io/helm/some-chart
version: 1.1.7

# or

chart: local/chart/path

# or
chart: uniquecr.azurecr.io/helm/some-chart
version: 1.1.7

After No login needed… simply:

chart: oci://ghcr.io/unique-ag/helm-charts/some-chart
version: 1.3.0

or

chart: https://unique-ag.github.io/helm-charts/some-chart
version: 1.3.0

Migrated charts

All charts used by Unique clients have been migrated:

Check out Artifact Hub to see them all. The image-pull-secret chart that Unique provides with the release will only be published and supported for a limited time (currently planned support up until release 2024.46). Afterwards Unique advises clients to mirror the images into their own registry and configure access to that registry from their k8s cluster (e.g.: ACR → use Managed Identity).