Skip to content
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: runtime tracing config value in helm chart should be disable #5009

Merged
merged 2 commits into from
Jul 10, 2023
Merged

fix: runtime tracing config value in helm chart should be disable #5009

merged 2 commits into from
Jul 10, 2023

Conversation

franco-bocci
Copy link

What this PR does / why we need it:
Fixing an inconsistency between the chart and the CRD.

Which issue(s) this PR fixes:
Fixes #5008

Special notes for your reviewer:
N/A

@seldondev
Copy link
Collaborator

Hi @franco-bocci. Thanks for your PR.

I'm waiting for a SeldonIO or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

@ukclivecox ukclivecox changed the title V2 fix: runtime tracing config value in helm chart should be disable Jul 10, 2023
@ukclivecox ukclivecox self-requested a review July 10, 2023 16:14
@ukclivecox ukclivecox merged commit ecfaafa into SeldonIO:v2 Jul 10, 2023
3 of 4 checks passed
@franco-bocci franco-bocci deleted the v2 branch July 10, 2023 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants