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
Bug 1879047: bump prometheus-operator 0.42 #928
Bug 1879047: bump prometheus-operator 0.42 #928
Conversation
s-urbaniak
commented
Sep 15, 2020
•
edited
edited
- I added CHANGELOG entry for this change.
- No user facing changes, so no entry in CHANGELOG was needed.
@s-urbaniak: This pull request references Bugzilla bug 1879047, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
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 kubernetes/test-infra repository. |
@s-urbaniak: This pull request references Bugzilla bug 1879047, which is valid. 3 validation(s) were run on this bug
In response to this:
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 kubernetes/test-infra repository. |
- [#928](https://github.com/openshift/cluster-monitoring-operator/pull/928) Bump prometheus-operator 0.42: | ||
- 0.42.0 changes: https://github.com/prometheus-operator/prometheus-operator/releases/tag/v0.42.0 | ||
- 0.41.1 changes: https://github.com/prometheus-operator/prometheus-operator/releases/tag/v0.41.1 | ||
- 0.41.0 changes: https://github.com/prometheus-operator/prometheus-operator/releases/tag/v0.41.0 |
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.
is this sufficient for us? 🤔
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.
Yes even just bump to Prometheus operator 0.42 would be enough. 👍
/cc @openshift/openshift-team-monitoring |
This e2e failure looks suspicious, investigating:
|
I cannot find anything suspicious in the logs, assuming network hiccups, hence retrying. |
/retest |
@@ -2,6 +2,10 @@ | |||
|
|||
## 4.6 | |||
|
|||
- [#928](https://github.com/openshift/cluster-monitoring-operator/pull/928) Bump prometheus-operator 0.42: | |||
- 0.42.0 changes: https://github.com/prometheus-operator/prometheus-operator/releases/tag/v0.42.0 | |||
- 0.41.1 changes: https://github.com/prometheus-operator/prometheus-operator/releases/tag/v0.41.1 |
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.
Those features are also included in 0.42, so including 0.41.1 changelog seems redundant
/test e2e |
1 similar comment
/test e2e |
assets/prometheus-operator-user-workload/0probe-custom-resource-definition.yaml
Outdated
Show resolved
Hide resolved
3cea4c2
to
e4e4323
Compare
/lgtm |
/hold |
there is one thing missing: the cluster role binding to be allowed to operate on |
@s-urbaniak should this be added in upstream or is this downstream patch we always do? |
@lilic it is already present in upstream, but we refer to 0.40 cluster role bindings here. I am a bit unsure if this mixture of 0.40 and 0.42 assets is a good idea tbh 🤔 it introduces quite some intricate complexity. |
changing strategy: we'll bump prometheus-operator 0.42 in |
We need to bump library-go because bitbucket.org/ww/goautoneg seized to exist.
f9fc6ee
to
ba670ce
Compare
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: s-urbaniak, simonpasquier The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test e2e-aws-operator |
/hold cancel |
/retest Please review the full test history for this PR and help us cut down flakes. |
/test e2e-aws-operator |
@s-urbaniak: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged:
These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Bugzilla bug 1879047 has not been moved to the MODIFIED state. In response to this:
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 kubernetes/test-infra repository. |