MON-3503: Synchronize versions of the downstream components

[openshift-monitoring-bot]

Description

This pull request updates jsonnet/versions.yaml to 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/version annotation) 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:

make versions
make generate

[openshift-ci]

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 /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 kubernetes/test-infra repository.

[slashpai]

/ok-to-test

[slashpai]

/lgtm

[raptorsun]

/label docs-approved
/label px-approved
/label jira/valid-reference

[openshift-ci]

@raptorsun: The label(s) /label jira/valid-reference cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, rebase/manual, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label docs-approved
/label px-approved
/label jira/valid-reference

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.

[slashpai]

/hold
Will wait for 0.69.1 release

[simonpasquier]

/skip

[simonpasquier]

Superseded by #2152.

[simonpasquier]

/lgtm

[simonpasquier]

/label acknowledge-critical-fixes-only

[simonpasquier]

/lgtm

[openshift-ci]

@openshift-monitoring-bot[bot]: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[simonpasquier]

/hold cancel

[simonpasquier]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-monitoring-bot[bot], simonpasquier, slashpai

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:

• OWNERS [simonpasquier,slashpai]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[simonpasquier]

/label px-approved
/label qe-approved
no functional change

[simonpasquier]

/retitle MON-3503: Synchronize versions of the downstream components

[openshift-ci-robot]

@openshift-monitoring-bot[bot]: This pull request references MON-3503 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set.

In response to this:

Description

This pull request updates jsonnet/versions.yaml to 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/version annotation) 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:

make versions
make generate

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.