Flyte v1.13.0-rc0

[davidmirror-ops]

Flyte v1.13.0-rc0 Release Notes

Major Features and Improvements

• Key-value execution tags: Enhanced execution tagging capabilities. (Key-value execution tags #5453)
• Watch agent metadata service: Improved monitoring of agent metadata. (Watch agent metadata service #5017)
• Distributed job refactoring: Refactored distributed job using common ReplicaSpec. ([Feature] Refactor distributed job using common ReplicaSpec #5355)
• Execution cluster label inheritance: Executions now inherit cluster labels from source executions. (Inherit execution cluster label from source execution #5431)
• Domain API: Added new API to retrieve domain information. (Add API to get domain #5443)
• Execution environment versioning: Added version to ExecutionEnv proto message. (Added version to ExecutionEnv proto message #5506)
• OTLP and sampling in otelutils: Enhanced observability with OpenTelemetry Protocol (OTLP) support. (Add OTLP and sampling to otelutils #5504)

Notable Changes

• Removed mmcloud plugin. (Remove mmcloud plugin #5468)
• Updated k3s version to 1.29.0. (Bump k3s version to 1.29.0 #5475)
• Improved auth flow to support custom base URLs in deployments. (fix: Modify the callback URL string in auth flow, to support custom base URLs in deployments #5192)
• Added flyteconsole URL to FlyteWorkflow CRD. (Add flyteconsole url to FlyteWorkflow CRD #5449)
• Enhanced 'flytectl compile' to consider launch plans within workflows. (Fix: Make 'flytectl compile' consider launchplans used within workflows #5463)
• Introduced control over task phases for log link display. (Feat: Allow controlling in which task phases log links are shown #4726)
• Improved Helm chart configurations for Prometheus, Webhook HPA, and Flyteconsole probes. (Helm chart updates related to Prometheus, Webhook HPA, and Flyteconsole probes #5508)

Bug Fixes and Optimizations

• Fixed flaky auto_refresh_test. (Fix flaky auto_refresh_test #5438)
• Corrected NULL to empty string in SQL insert for migrations. (fix(migrations): Correct NULL to empty string in SQL insert #5482)
• Resolved issues with broken mermaid diagrams in documentation. (fix broken mermaid diagrams #5498)
• Fixed Ray plugin to use default service account if not set in task metadata. (fix(ray): Use default svc account if not set in task metadata #5499)

Documentation and Usability

• Updated community page. (Update community page #5496)
• Improved documentation on logging link lifetime configuration. (Doc: Explain how lifetime of logging links is configured #5503)
• Replaced 'uctl' with 'flytectl' in OSS docs for consistency. (Fix: replace uctl with flytectl in OSS docs #5501)

New Contributors

• @Dlougach, @flixr, @trevormcguire, @va6996, @mhotan, and @eltociear made their first contributions to the project.

For a complete list of changes, please refer to the full changelog.

---

Add your feedback below.

Thanks!

[corleyma]

re: Key-value execution tags;

I saw this PR after it merged. One thing I wasn't clear on is whether the supported query params allow filtering for specific key-value combinations. As implemented, is it possible to list workflow executions with a tag of (key) Foo = (value) Bar AND a tag of (key) Baz = (value) Qux?

The examples in the MR make it look like we can list workflows that have certain keys, and workflows that have certain values, and we can intersect those, but it wasn't clear if you can list workflows where a specific key has a specific value (useful in the case where you're trying to list by multiple key/value pairs).

Also, looking at the bigger tracking issue, there are plans to add this functionality to the UI and an old MR from before the addition of key/value tags. Curious if the UI changes are also planned for this release, or if there is a particular plan for the UI design that folks can help contribute to...

[davidmirror-ops]

cc @pingsutw

[pingsutw]

is it possible to list workflow executions with a tag of (key) Foo = (value) Bar AND a tag of (key) Baz = (value) Qux?

@corleyma We do support that. Here is an example

https://<host_name>/api/v1/executions/flytesnacks/development?filters=contains(execution_tag.key,rust1)%2Bcontains(execution_tag.value,2)&limit=25&sort_by.direction=DESCENDING&sort_by.key=created_at

[pingsutw]

if there is a particular plan for the UI design that folks can help contribute to...

We have an initial design internally. we'll share it with you