Platform Release Notes

Gretel's Platform is comprised of control plane and data plane components.

The Gretel Data Plane is responsible for processing user-provided prompts and/or datasets and generating synthetic data.

The Gretel Control Plane includes Gretel's APIs, job scheduling, and workflow management.

Release Schedule and Versioning

Gretel generally releases platform updates every Tuesday. We do sometimes release out-of-band to address critical bug fixes, security updates, or pre-releases for future features and capabilities.

Gretel follows a CalVer versioning schema. The schema is YYYY.MM.N:

• YYYY: Calendar year.

• MM: Month of year.

• N: Monotonically increasing release number for the given month, so 2024.6.1 is the first release in June of 2024.

Gretel Cloud

Gretel automatically upgrades the Gretel Cloud to support enhancements and upgrades to the platform. All users get the same updates at the same time. Gretel uses the CalVer internally to track the changes and release notes are organized by these CalVer numbers to more easily communicate changes that are delivered.

Gretel Hybrid

Gretel Hybrid splits the control and data planes such that:

• Gretel maintains and runs the control plane in Gretel Cloud. Gretel control plane updates are automatically shipped by Gretel for both Gretel Hybrid and Gretel Cloud.

• The data plane is customer managed within customer cloud accounts. Depending on your Hybrid setup, you will need to update varying container images. More on this below.

All container image versions for Hybrid are tagged with the same CalVer number on each release. The concrete release notes are organized by version number, these version numbers should be used to update your container images as necessary.

The container images used on Gretel Hybrid can be split into three categories:

• Management containers. Images are prefixed with gcc-. There are three core management containers that run on the Hybrid cluster. These containers are responsible for managing model jobs and workflows.

• Workflow container. This container image is named workflow. These containers are used when running Gretel Workflows and handle things such as source and sink actions.

• Model container. This container image is named model. These are containers that run the actual Gretel models for generating synthetic data.

If your Hybrid deployment directly uses Gretel's container registry or a pull through cache the workflow and model container images are automatically updated and pulled for you upon release. These containers are spawned by the management containers during model jobs and workflow runs.

Gretel's container images have several shared internal libraries. We have consolidated the number of total images to make upgrades easier. We highly recommend upgrading all container images at the same time based on release version numbers. This mirrors how we update Gretel Cloud.

Image Mirrors

If you need to explicitly pull images by tag and cannot use the latest tag, then you should use the appropriate CalVer version number for the image tag.