Skip to content

Conversation

@Pkylas007
Copy link

@Pkylas007 Pkylas007 commented May 28, 2025

Version(s):

  • OCP 4.20, 4.19

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

Note -
As discussed with Kathryn, skipping the QE review because this PR focuses on adding a space after the include statements in modules and there are no technical changes.

Additional information:

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 28, 2025
@Pkylas007 Pkylas007 force-pushed the oadp-5888-space-after-include branch from 8a1cf5b to 3db2bd3 Compare June 25, 2025 09:07
@Pkylas007
Copy link
Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Jun 26, 2025
@lahinson lahinson added peer-review-in-progress Signifies that the peer review team is reviewing this PR branch/enterprise-4.19 branch/enterprise-4.20 and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Jun 26, 2025
@lahinson lahinson added this to the Continuous Release milestone Jun 26, 2025
Copy link
Contributor

@lahinson lahinson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM


[id="oadp-different-kubernetes-api-versions"]
== Working with different Kubernetes API versions on the same cluster

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is out of the scope of this PR, but this section needs a short introduction. Otherwise, you end up with one heading being displayed just after another heading.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also part of CQA 2.0 work for migration and will need to be done at some point as I understand.

include::modules/oadp-using-enable-api-group-versions.adoc[leveloffset=+2]

[id="backing-up-data-one-cluster-restoring-another-cluster"]
== Backing up data from one cluster and restoring it to another cluster
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar comment as above -- it would be good to add a short introduction here.


[id="oadp-storage-class-mapping"]
== OADP storage class mapping

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar comment as above -- it would be good to add a short introduction here.

@lahinson lahinson added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jun 26, 2025
@openshift-ci openshift-ci bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 9, 2025
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 8, 2025
@bergerhoffer
Copy link
Contributor

The branch/enterprise-4.21 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.20. And any PR going into main must also target the latest version branch (enterprise-4.21).

If the update in your PR does NOT apply to version 4.21 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

@Pkylas007
Copy link
Author

The branch/enterprise-4.21 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.20. And any PR going into main must also target the latest version branch (enterprise-4.21).

If the update in your PR does NOT apply to version 4.21 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

Thank you @anahas-redhat !

@Pkylas007
Copy link
Author

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 21, 2025
@Pkylas007
Copy link
Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Oct 21, 2025
[id="openshift-adp-controller-manager-seg-fault_{context}"]
= OpenShift ADP Controller segmentation fault

If you configure a DPA with both `cloudstorage` and `restic` enabled, the `openshift-adp-controller-manager` pod crashes and restarts indefinitely until the pod fails with a crash loop segmentation fault.
Copy link
Contributor

@JoeAldinger JoeAldinger Oct 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

*ADP
You need nouns after the literals cloudstorage and restic unless they are values.

Copy link
Contributor

@JoeAldinger JoeAldinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One comment to address.

@JoeAldinger JoeAldinger removed the merge-review-needed Signifies that the merge review team needs to review this PR label Oct 21, 2025
@Pkylas007
Copy link
Author

One comment to address.

Hi @JoeAldinger ,

Thank you for your comment. I'll inform the OADP team but I'm not allowed to make any content change in OADP documentation. It's beyond the scope of this PR. Could you merge this PR please?

//
// applications/projects/working-with-projects.adoc

:_mod-docs-content-type: PROCEDURE
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't look like a procedure module to me. Is it a concept?

@JoeAldinger
Copy link
Contributor

One comment to address.

Hi @JoeAldinger ,

Thank you for your comment. I'll inform the OADP team but I'm not allowed to make any content change in OADP documentation. It's beyond the scope of this PR. Could you merge this PR please?

Hi this actually belongs to @anarnold97 and the aligned team. The PR has a few deal breakers from OCP's perspective including 3 commits that need squashed, a QE ack for the procedure and concept module, and I don't think either new module follows our guidelines for a procedure (there aren't any steps) and concept module (i.e. a NOTE callout isn't a concept module). Get with Andy and he can help you.

@anarnold97
Copy link
Contributor

@shdeshpa07 - please can you have a look at this PR and give @Pkylas007 some guidance

Thanks

@shdeshpa07
Copy link
Contributor

@shdeshpa07 - please can you have a look at this PR and give @Pkylas007 some guidance

Thanks

Hi @anarnold97 and @Pkylas007 - Would it be better if I just take over the PR, work through the review comments and merge it after? Also, does this PR cover all the work for the DITA work for OADP doc set 1? If so, I will also back port it to 4.14. Thanks.

@Pkylas007
Copy link
Author

Pkylas007 commented Oct 27, 2025

@shdeshpa07 - please can you have a look at this PR and give @Pkylas007 some guidance
Thanks

Hi @anarnold97 and @Pkylas007 - Would it be better if I just take over the PR, work through the review comments and merge it after? Also, does this PR cover all the work for the DITA work for OADP doc set 1? If so, I will also back port it to 4.14. Thanks.

Hi @shdeshpa07 This PR should not contain changes to content because it's a part of a specific modularization effort. However, if you think that's what OCP needs, then please go ahead: make content changes. Thanks!

DITA work for set 1 has only this PR.

@Pkylas007 Pkylas007 closed this Oct 27, 2025
@Pkylas007 Pkylas007 reopened this Oct 27, 2025
@shdeshpa07
Copy link
Contributor

@shdeshpa07 - please can you have a look at this PR and give @Pkylas007 some guidance
Thanks

Hi @anarnold97 and @Pkylas007 - Would it be better if I just take over the PR, work through the review comments and merge it after? Also, does this PR cover all the work for the DITA work for OADP doc set 1? If so, I will also back port it to 4.14. Thanks.

Hi @shdeshpa07 This PR should not contain changes to content because it's a part of a specific modularization effort. However, if you think that's what OCP needs, then please go ahead: make content changes. Thanks!

DITA work for set 1 has only this PR.

@Pkylas007 - Thanks. You are correct. THere should be no content changes. I am yet to look into detail what the specific comments are. But, apart from the content changes, is there is any specific guidance you need from me? If not, could you squash the commits please, so I can do a quick review and merge it :).

Fixed validation errors

Update modules/oadp-adp-controller-segmentation.adoc

Co-authored-by: Andy Arnold <[email protected]>

Removed asciidoctor files
@Pkylas007 Pkylas007 force-pushed the oadp-5888-space-after-include branch from 7cc5cf7 to f25dce0 Compare October 27, 2025 09:49
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 27, 2025
@openshift-merge-robot
Copy link

PR needs rebase.

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.

@Pkylas007
Copy link
Author

@shdeshpa07 - please can you have a look at this PR and give @Pkylas007 some guidance
Thanks

Hi @anarnold97 and @Pkylas007 - Would it be better if I just take over the PR, work through the review comments and merge it after? Also, does this PR cover all the work for the DITA work for OADP doc set 1? If so, I will also back port it to 4.14. Thanks.

Hi @shdeshpa07 This PR should not contain changes to content because it's a part of a specific modularization effort. However, if you think that's what OCP needs, then please go ahead: make content changes. Thanks!
DITA work for set 1 has only this PR.

@Pkylas007 - Thanks. You are correct. THere should be no content changes. I am yet to look into detail what the specific comments are. But, apart from the content changes, is there is any specific guidance you need from me? If not, could you squash the commits please, so I can do a quick review and merge it :).

@shdeshpa07 Thank you :) I've squashed the commits.

@openshift-ci
Copy link

openshift-ci bot commented Oct 27, 2025

@Pkylas007: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/validate-portal f25dce0 link true /test validate-portal
ci/prow/validate-asciidoc f25dce0 link true /test validate-asciidoc

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.

@Pkylas007
Copy link
Author

@shdeshpa07 The include statements in the modules added in this PR have the necessary 1-line spacing in the main branch. Hence, I'm closing this PR as it is redundant. Thanks for looking into this!

@Pkylas007 Pkylas007 closed this Oct 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.19 branch/enterprise-4.20 branch/enterprise-4.21 needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants