Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Sovietaced
Copy link
Member

@Sovietaced Sovietaced commented May 12, 2025

Tracking issue

Closes #6446

Why are the changes needed?

This allows users to customize the rollout strategy of different flyte components.

What changes were proposed in this pull request?

Makes the rollout strategy configurable for different flyte components.

How was this patch tested?

It was not tested.

Setup process

Screenshots

Check all the applicable boxes

  • I updated the documentation accordingly.
  • All new and existing tests passed.
  • All commits are signed-off.

Related PRs

Docs link

Summary by Bito

This pull request enhances Flyte deployment flexibility by introducing configurable rollout strategies for various components, including updates to deployment YAML files and adjustments to secrets and checksums. These modifications aim to improve customization and streamline the deployment process.

Unit tests added: False

Estimated effort to review (1-5, lower is better): 2 - The changes are straightforward and well-documented, making the review process relatively quick.

@flyte-bot
Copy link
Collaborator

Code Review Agent Run Status

  • Limitations and other issues: ❌ Failure - Bito Automatic Review Skipped - Draft PR

    Bito didn't auto-review because this pull request is in draft status.
    To trigger review, mark the PR as ready or type /review in the comment and save.
    You can change draft PR review settings here, or contact the agent instance creator at [email protected].

@codecov
Copy link

codecov bot commented May 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.47%. Comparing base (7409797) to head (081bc2e).
Report is 6 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #6447   +/-   ##
=======================================
  Coverage   58.47%   58.47%           
=======================================
  Files         940      940           
  Lines       71579    71579           
=======================================
  Hits        41858    41858           
  Misses      26538    26538           
  Partials     3183     3183           
Flag Coverage Δ
unittests-datacatalog 59.03% <ø> (ø)
unittests-flyteadmin 56.24% <ø> (ø)
unittests-flytecopilot 30.99% <ø> (ø)
unittests-flytectl 64.72% <ø> (ø)
unittests-flyteidl 76.12% <ø> (ø)
unittests-flyteplugins 60.95% <ø> (ø)
unittests-flytepropeller 54.78% <ø> (ø)
unittests-flytestdlib 64.02% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Sovietaced Sovietaced added the added Merged changes that add new functionality label May 12, 2025
@Sovietaced Sovietaced marked this pull request as ready for review May 12, 2025 13:18
@Sovietaced Sovietaced changed the title Allow rollout strategy to be configured Allow rollout strategy to be configured in Helm charts May 12, 2025
@Sovietaced Sovietaced merged commit 6867209 into flyteorg:master May 18, 2025
54 checks passed
@Sovietaced Sovietaced deleted the issue-6446 branch May 18, 2025 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

added Merged changes that add new functionality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Core feature] Allow rollout strategy to be configurable in Helm charts

3 participants