OSDOCS-17043: revert erroneously propagated deprecation#107812
OSDOCS-17043: revert erroneously propagated deprecation#107812jeana-redhat wants to merge 1 commit intoopenshift:enterprise-4.18from
Conversation
|
@jeana-redhat: This pull request references OSDOCS-17043 which is a valid 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. |
|
@jeana-redhat: This pull request references OSDOCS-17043 which is a valid 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. |
022d9d7 to
f8e6e53
Compare
|
@jeana-redhat: This pull request references OSDOCS-17043 which is a valid 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. |
|
@jeana-redhat: all tests passed! 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. |
Version(s):
4.16-4.18
Issue:
OSDOCS-17043
Link to docs preview:
QE review:
N/A
Additional information:
Discovered while manually cherrypicking of #103103 into 4.19 that the manual picks for 4.16-4.18 propagated a 4.20+ deprecation notice (ref: #99963) into earlier content as part of merge conflict resolution. This reverts that change to the appropriate pre-4.20 state. Confirmed dep status as 4.20+ with @skopacz1 🙇