-
Notifications
You must be signed in to change notification settings - Fork 41
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
feat: bump Observability Operator version to v4.0.0 #1423
feat: bump Observability Operator version to v4.0.0 #1423
Conversation
@vmanley I don't think this needs to be a draft. Let's get v3.0.16 on stage before the next Prod release. |
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.
The change looks good to me.
Can we follow suit with this one by bumping https://github.com/bf2fc6cc711aee1a0c2a/kas-installer/blob/main/kas-installer-defaults.env#L127 to the latest tag that contains this change as well as updating https://github.com/bf2fc6cc711aee1a0c2a/kas-installer/blob/main/kas-installer-defaults.env#L145 to match the latest KFM commit sha? Thanks
c67c81b
to
d01f186
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1423 +/- ##
=======================================
Coverage 83.31% 83.31%
=======================================
Files 143 143
Lines 12794 12794
=======================================
Hits 10659 10659
Misses 1753 1753
Partials 382 382
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@pb82 @machi1990 Bumped to v4.0.0. Verified on cluster. Could I get one of you to merge? |
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.
lgtm
I'd also like @pb82 to give his blessings on this.
Please lets also followup in updating kas-installer
Description
Bump the version of Observability Operator to v4.0.0
Verification Steps
Checklist (Definition of Done)
All acceptance criteria specified in JIRA have been completedUnit and integration tests added that prove the fix is effective or the feature works (tested against emulated and non-emulated OCM environment)Documentation added for the featureRequired metrics/dashboards/alerts have been added (or PR created).Required Standard Operating Procedure (SOP) is added.JIRA has been created for changes required on the client side