SREP-2513: add CAD PagerDuty Integration Key secret

[MateSaary]

What type of PR is this?

feat

What this PR does / why we need it?

This PR patches the existing pd-secret in openshift-monitoring ns to include a CAD_PAGERDUTY_KEY for use by https://github.com/openshift/configure-alertmanager-operator/pull/456

Which Jira/Github issue(s) this PR fixes?

Fixes #

Special notes for your reviewer:

Pre-checks (if applicable):

• [x] Tested latest changes against a cluster

• [x] Included documentation changes with PR

• [x] If this is a new object that is not intended for the FedRAMP environment (if unsure, please reach out to team FedRAMP), please exclude it with:

  matchExpressions:
  - key: api.openshift.com/fedramp
    operator: NotIn
    values: ["true"]
  

[openshift-ci-robot]

@MateSaary: This pull request references SREP-2442 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 story to target the "4.21.0" version, but no target version was set.

In response to this:

What type of PR is this?

feat

What this PR does / why we need it?

This PR patches the existing pd-secret in openshift-monitoring ns to include a CAD_PAGERDUTY_KEY for use by https://github.com/openshift/configure-alertmanager-operator/pull/456

Which Jira/Github issue(s) this PR fixes?

Fixes #

Special notes for your reviewer:

Pre-checks (if applicable):

• [x] Tested latest changes against a cluster

• [x] Included documentation changes with PR

• [x] If this is a new object that is not intended for the FedRAMP environment (if unsure, please reach out to team FedRAMP), please exclude it with:

  matchExpressions:
  - key: api.openshift.com/fedramp
    operator: NotIn
    values: ["true"]
  

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

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: MateSaary Once this PR has been reviewed and has the lgtm label, please assign smarthall for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci[bot]]

@MateSaary: 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-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@MateSaary: This pull request references SREP-2513 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 story to target the "4.21.0" version, but no target version was set.

In response to this:

What type of PR is this?

feat

What this PR does / why we need it?

This PR patches the existing pd-secret in openshift-monitoring ns to include a CAD_PAGERDUTY_KEY for use by https://github.com/openshift/configure-alertmanager-operator/pull/456

Which Jira/Github issue(s) this PR fixes?

Fixes #

Special notes for your reviewer:

Pre-checks (if applicable):

• [x] Tested latest changes against a cluster

• [x] Included documentation changes with PR

• [x] If this is a new object that is not intended for the FedRAMP environment (if unsure, please reach out to team FedRAMP), please exclude it with:

  matchExpressions:
  - key: api.openshift.com/fedramp
    operator: NotIn
    values: ["true"]
  

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.

[MateSaary]

Closing in favour of agreed upon re-implementation: https://issues.redhat.com/browse/SREP-2513