Skip to content

Releases: Netflix/metaflow

2.17.1

11 Aug 21:08
e72508a
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.17.0...2.17.1

2.17.0

05 Aug 22:46
27c6aae
Compare
Choose a tag to compare

Improvements

Argo Workflows name length restriction

This release introduces a limit to the workflow name lengths that are deployed to Argo Workflows.

Why was this necessary?

Argo Workflows attaches the workflow template name (the deployed flow name) as a label to the Kubernetes resources it creates when argo itself launches a flow (events, schedule, Argo UI). The problem is that Kubernetes labels have a maximum length of 63 characters, and if a workflow name is longer than that, it will fail to launch due to not fitting in the label.

Launching flows on Argo Workflows through the Metaflow CLI has always been exempt of this issue, as this has not tried to attach such a label to the resources.

What about existing flows?

Existing flows continue to operate as previously, and these can still be operated on with the Metaflow CLI commands, e.g. argo-workflows trigger/argo-workflows delete.

An existing flow will always be replaced when running argo-workflows create. With the new version this might also result in a differently named deployment, in case the old one had a name that was too long.

What happens with long names now?

When using the @project decorator, Metaflow will automatically truncate the deployed name if it is too long. A part of each name partial (project / branch / flow_name) is kept to help with finding the deployments in Argo UI.

If the name of the deployment is too long when deploying without @project, then this is treated as an error and it is up to the user to provide a shorter name. This can be done by either renaming the flow class, or by supplying a custom name with --name

⚠️ NOTE
Deploying the same flow with an older version of Metaflow will lead to two separate deployments existing at once if the length of the name exceeded the limit.
For such flows be sure to only deploy them with Metaflow versions >=2.17 or use the --name CLI option to specify a custom deploy name.

What's Changed

Full Changelog: 2.16.8...2.17.0

2.16.8

29 Jul 18:11
6138942
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.16.7...2.16.8

2.16.7

29 Jul 00:26
2e98823
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.16.6...2.16.7

2.16.6

24 Jul 17:56
6cd6a39
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.16.5...2.16.6

2.16.5

21 Jul 19:40
7fa9a1e
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 2.16.4...2.16.5

2.16.4

17 Jul 17:32
f56211e
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.16.3...2.16.4

2.16.3

16 Jul 14:22
2c702e1
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.16.2...2.16.3

2.16.2

15 Jul 22:31
a583a0c
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.16.1...2.16.2

2.16.1

15 Jul 18:31
68df8e4
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.16.0...2.16.1