Add node toleration to alertmanager and prometheus pods

[rohan47]

Platform related metrics and alerts pods deployed by ODF do not have spec.tolerations with node.ocs.openshift.io/storage when taint nodes performed. This PR adds the required tolerations

[openshift-ci-robot]

@rohan47: This pull request references [Jira Issue DFBUGS-1272](https://issues.redhat.com//browse/DFBUGS-1272), which is invalid:

• expected the bug to target the "odf-4.18" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Platform related metrics and alerts pods deployed by ODF do not have spec.tolerations with node.ocs.openshift.io/storage when taint nodes performed. This PR adds the required tolerations

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.

[openshift-ci]

Hi @rohan47. Thanks for your PR.

I'm waiting for a red-hat-storage 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-sigs/prow repository.

[openshift-ci-robot]

@rohan47: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

Platform related metrics and alerts pods deployed by ODF do not have spec.tolerations with node.ocs.openshift.io/storage when taint nodes performed. This PR adds the required tolerations

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.

[ezio-auditore]

Changes looks good. Please verify changes if it is working as it should

[iamniting]

/ok-to-test

[openshift-ci-robot]

@rohan47: This pull request references [Jira Issue DFBUGS-1272](https://issues.redhat.com//browse/DFBUGS-1272), which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (odf-4.18) matches configured target version for branch (odf-4.18)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

Platform related metrics and alerts pods deployed by ODF do not have spec.tolerations with node.ocs.openshift.io/storage when taint nodes performed. This PR adds the required tolerations

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.

[rohan47]

/jira refresh

[openshift-ci-robot]

@rohan47: This pull request references [Jira Issue DFBUGS-1272](https://issues.redhat.com//browse/DFBUGS-1272), which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (odf-4.18) matches configured target version for branch (odf-4.18)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

/jira refresh

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.

[iamniting]

@rohan47 bugs are not required for the main branch. We only need them to backport.

[openshift-ci-robot]

@rohan47: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

Platform related metrics and alerts pods deployed by ODF do not have spec.tolerations with node.ocs.openshift.io/storage when taint nodes performed. This PR adds the required tolerations

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.

[iamniting]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@iamniting: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.18

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.

[iamniting]

@rohan47 @ezio-auditore Is the PR tested?

[rohan47]

The PR is tested @iamniting

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iamniting, rohan47

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 [iamniting]

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

[openshift-cherrypick-robot]

@iamniting: new pull request created: #2988

In response to this:

/cherry-pick release-4.18

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.