OADP-3145: OADP 1.3.0 Attributes Updates

[anarnold97]

Jira

• OADP-3145 - see Slack discussion

  • Velero version moves to 1.12 to OADP 1.3.0

  

Version(s):

• OCP 4.12 → branch/enterprise-4.12
• OCP 4.13 → branch/enterprise-4.13
• OCP 4.14 → branch/enterprise-4.14
• OCP 4.15 → branch/enterprise-4.15

Link to docs preview:

• OADP-Velero-OpenShift Container Platform version relationship

QE review:

• QE has approved this change.

Additional information:

[openshift-ci-robot]

@anarnold97: This pull request references OADP-3145 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 either version "4.15." or "openshift-4.15.", but it targets "OADP 1.3.0" instead.

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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.

[anarnold97]

/label oadp

[ocpdocs-previewbot]

🤖 Updated build preview is available at:
https://68597--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/35170

[openshift-ci-robot]

@anarnold97: This pull request references OADP-3145 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 either version "4.15." or "openshift-4.15.", but it targets "OADP 1.3.0" instead.

In response to this:

Jira

• OADP-3145

** Velero version moves to 1.12 to OADP 1.3.0

Version(s):

• OCP 4.12 → branch/enterprise-4.12
• OCP 4.13 → branch/enterprise-4.13
• OCP 4.14 → branch/enterprise-4.14
• OCP 4.15 → branch/enterprise-4.15

Link to docs preview:

• OADP-Velero-OpenShift Container Platform version relationship

QE review:

• QE has approved this change.

Additional information:

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.

[openshift-ci-robot]

@anarnold97: This pull request references OADP-3145 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 either version "4.15." or "openshift-4.15.", but it targets "OADP 1.3.0" instead.

In response to this:

Jira

• OADP-3145

  • Velero version moves to 1.12 to OADP 1.3.0

Version(s):

• OCP 4.12 → branch/enterprise-4.12
• OCP 4.13 → branch/enterprise-4.13
• OCP 4.14 → branch/enterprise-4.14
• OCP 4.15 → branch/enterprise-4.15

Link to docs preview:

• OADP-Velero-OpenShift Container Platform version relationship

QE review:

• QE has approved this change.

Additional information:

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.

[openshift-ci-robot]

@anarnold97: This pull request references OADP-3145 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 either version "4.15." or "openshift-4.15.", but it targets "OADP 1.3.0" instead.

In response to this:

Jira

• OADP-3145

  • Velero version moves to 1.12 to OADP 1.3.0

  

Version(s):

• OCP 4.12 → branch/enterprise-4.12
• OCP 4.13 → branch/enterprise-4.13
• OCP 4.14 → branch/enterprise-4.14
• OCP 4.15 → branch/enterprise-4.15

Link to docs preview:

• OADP-Velero-OpenShift Container Platform version relationship

QE review:

• QE has approved this change.

Additional information:

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.

[openshift-ci-robot]

@anarnold97: This pull request references OADP-3145 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 either version "4.15." or "openshift-4.15.", but it targets "OADP 1.3.0" instead.

In response to this:

Jira

• OADP-3145 - see Slack discussion

  • Velero version moves to 1.12 to OADP 1.3.0

  

Version(s):

• OCP 4.12 → branch/enterprise-4.12
• OCP 4.13 → branch/enterprise-4.13
• OCP 4.14 → branch/enterprise-4.14
• OCP 4.15 → branch/enterprise-4.15

Link to docs preview:

• OADP-Velero-OpenShift Container Platform version relationship

QE review:

• QE has approved this change.

Additional information:

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.

[anarnold97]

/label peer-review-needed

[anarnold97]

Am I ok to push this to peer-review without QE sign-off? No problems if necessary

[mburke5678]

@anarnold97 LGTM. Please get QE review before merge review.

[anarnold97]

@mburke5678 Will do! I am sure the one and only customer on OADP 1.3 can wait to know they are using 1.12 not 1.11 (LOL)

[anarnold97]

/label merge-review-required

[openshift-ci]

@anarnold97: The label(s) /label merge-review-required 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, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, peer-review-done, peer-review-in-progress, peer-review-needed, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label merge-review-required

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.

[anarnold97]

/label merge-review-needed

[kalexand-rh]

/cherrypick enterprise-4.15

[kalexand-rh]

/cherrypick enterprise-4.14

[kalexand-rh]

/cherrypick enterprise-4.13

[kalexand-rh]

/cherrypick enterprise-4.12

[openshift-cherrypick-robot]

@kalexand-rh: new pull request created: #68640

In response to this:

/cherrypick enterprise-4.15

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.

[openshift-cherrypick-robot]

@kalexand-rh: new pull request created: #68641

In response to this:

/cherrypick enterprise-4.14

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.

[openshift-cherrypick-robot]

@kalexand-rh: new pull request created: #68642

In response to this:

/cherrypick enterprise-4.13

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.

[openshift-cherrypick-robot]

@kalexand-rh: new pull request created: #68643

In response to this:

/cherrypick enterprise-4.12

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.