-
Notifications
You must be signed in to change notification settings - Fork 384
NO-JIRA: [bot] Synchronize versions of the downstream components #2615
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
NO-JIRA: [bot] Synchronize versions of the downstream components #2615
Conversation
|
Hi @openshift-monitoring-bot[bot]. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
7dbb070 to
52bf569
Compare
slashpai
left a comment
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.
/ok-to-test
/lgtm
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
52bf569 to
63fb002
Compare
|
@openshift-monitoring-bot[bot]: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
|
/testwith openshift/cluster-monitoring-operator/main/e2e-aws-ovn-techpreview openshift/origin#29975 |
|
/lgtm |
|
@openshift-monitoring-bot[bot]: This pull request explicitly references no jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: machine424, openshift-monitoring-bot[bot], slashpai The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@machine424: Overrode contexts on behalf of machine424: ci/prow/e2e-aws-ovn-techpreview DetailsIn 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-sigs/prow repository. |
|
/skip ci/prow/e2e-aws-ovn-single-node |
26f9666
into
openshift:main
|
[ART PR BUILD NOTIFIER] Distgit: cluster-monitoring-operator |
Description
This pull request updates
jsonnet/versions.yamlto match with the already in use downstream versions of the monitoring components.Based on that file, it regenerates the assets to update some metadata (mainly the
app.kubernetes.io/versionannotation) attached to some of the resources and update other placeholders.It is safe to merge this change (provided that the CI jobs pass).
If you wish to perform this manually, execute the following commands from cluster-monitoring-operator repository: