-
Notifications
You must be signed in to change notification settings - Fork 750
Make it possible to configure flyte with an externally managed Secret #5700
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it possible to configure flyte with an externally managed Secret #5700
Conversation
Signed-off-by: Mike Hotan <[email protected]>
75c3fcb
to
9b7a65c
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5700 +/- ##
==========================================
- Coverage 37.07% 37.06% -0.01%
==========================================
Files 1318 1318
Lines 132652 132652
==========================================
- Hits 49175 49169 -6
- Misses 79228 79234 +6
Partials 4249 4249
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff thank you!
Sorry for the delays in the review. Could you address the conflicts to merge?
Code Review Agent Run #0b34fdActionable Suggestions - 0Review Details
|
Changelist by BitoThis pull request implements the following key changes.
|
Tracking issue
N/A
Why are the changes needed?
Union manages flyte-core helm release via ArgoCD. We identified that managing the oath client secret was appropriate outside of the flyte-core helm release and, thus, outside of a Git repository watched by ArgoCD. This situation will likely surface for other flyte users. We are thus backporting these changes from Union to Flyte OSS.
How was this patch tested?
This change was tested and release to all Union managed data planes.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link
Summary by Bito
This pull request introduces a feature improvement by making the admin OAuth client credentials' secret name configurable, allowing for external management by tools like ArgoCD. It also updates shared secrets and checksum values in several YAML manifest files.Unit tests added: False
Estimated effort to review (1-5, lower is better): 2