-
Notifications
You must be signed in to change notification settings - Fork 674
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
Fix minio config on helpers.tpl #5018
Fix minio config on helpers.tpl #5018
Conversation
Signed-off-by: davidmirror-ops <david [email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5018 +/- ##
=======================================
Coverage 58.99% 59.00%
=======================================
Files 645 645
Lines 55542 55542
=======================================
+ Hits 32769 32770 +1
+ Misses 20182 20181 -1
Partials 2591 2591
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: davidmirror-ops <david [email protected]>
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.
This was put in place initially to accommodate fast registration in the legacy sandbox. In the demo cluster (i.e. the current sandbox) we override that value separately.
We're in the process of removing the legacy sandbox, so I'm wondering if we shouldn't go through the effort of setting up a separate helm chart for the on-prem scenario. Not for this PR obviously.
@eapolinario I've considered a chart for on-prem too. The problem is that it'd be hard to design it following Helm conventions, especially considering how many options are available to achieve the same thing in the on prem world. For example, what default values to set for Ingress? for what controller? Also, what if someone is not using minio? (they can go with custom, which is not greatly documented but that's a different problem). |
* Fix sandbox endpoint Signed-off-by: davidmirror-ops <david [email protected]> * Make Helm Signed-off-by: davidmirror-ops <david [email protected]> --------- Signed-off-by: davidmirror-ops <david [email protected]> Co-authored-by: davidmirror-ops <david [email protected]>
Tracking issue
Closes #5004
Why are the changes needed?
What changes were proposed in this pull request?
How was this patch tested?
Deployed to an on-prem K8s cluster with minio and it successfully executes workflows.
I used
storage.type: sandbox
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link