ROX-33550: Add doc links for operator install and deprecation notices#19554
ROX-33550: Add doc links for operator install and deprecation notices#19554
Conversation
|
Skipping CI for Draft Pull Request. |
|
Images are ready for the commit at a455f7e. To use with deploy scripts, first |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #19554 +/- ##
==========================================
- Coverage 49.32% 49.32% -0.01%
==========================================
Files 2737 2737
Lines 206445 206445
==========================================
- Hits 101837 101829 -8
- Misses 97065 97070 +5
- Partials 7543 7546 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
porridge
left a comment
There was a problem hiding this comment.
LGTM but I agree a platform-agnostic operator install doc landing page would be better.
26a7a02 to
22703ad
Compare
8d1711c to
b1b2338
Compare
| <a | ||
| href={getVersionedDocs( | ||
| version, | ||
| 'installing/installing-rhacs-on-red-hat-openshift#install-secured-cluster-ocp' |
There was a problem hiding this comment.
@kcarmichael08 We’ve added doc links to the deprecation notices on the Helm and manifest install pages. Each deprecation alert now links to "operator installation documentation" so users have a clear migration path.
Currently, the link points to the OpenShift operator install page (installing-rhacs-on-red-hat-openshift#install-secured-cluster-ocp). Two questions:
- Is there a platform-agnostic operator install page we should link to instead?
- If not, should we show two links (one for OpenShift, one for other platforms) rather than just the OpenShift one?
There was a problem hiding this comment.
- No, there is no Operator install for non-OCP since that feature isn't available yet.
- I hesitate to put in narrowly-targeted hardcoded links (even if we could guess what the link structure would be) because we will be changing our whole publishing system in summer 2026 so any links would need to be changed again. We can put in redirects, but the fewer ones that we have to redirect, the better.
For now, I think linking to OCP Operator installation docs is OK.
There was a problem hiding this comment.
- No, there is no Operator install for non-OCP since that feature isn't available yet.
Well, I think at this point it's available enough to be documentable. See this ticket.
There was a problem hiding this comment.
Yes, but that ticket was created two days ago, so there is no documentation available yet to add a link for in the GUI. So I cannot provide a link to documentation that is not yet created.
The parent ticket of ROX-33749 is a 4.11 ticket, so it would typically be done in the 4.11 cycle (which has not yet started for docs - as you know, our work lags behind development). When you say "enough to be documentable," were you expecting something now, before 4.11 docs are published?
There was a problem hiding this comment.
That makes sense, Kerry. I don't think the intention of this PR is to assume that the docs are already in place. Just setting things up so that when the docs come in, we already have everything set up on the UI. If the external link still needs to be decided, we can either leave a comment in JIRA to revisit this and update the link or keep this open until that is decided.
There was a problem hiding this comment.
Good idea! We should have a better idea of the link after the drafts are done.
Until those docs are created and published, we can't provide a link. You could link to the overall "installation page" instead, which is not as targeted, but would at least get users to the correct overall page and they can scroll, look through the TOC, or search in the page to look for the Operator for Kubernetes system instructions when they are published. |
…tices Add non-OpenShift documentation links to the operator installation instructions page and link deprecation alerts to operator install docs so users can easily find migration guidance. Signed-off-by: Saif Chaudhry <schaudhr@redhat.com>
Deduplicate the identical deprecation alert block that was repeated across three cluster installation pages into a shared component. Signed-off-by: Saif Chaudhry <schaudhr@redhat.com>
Line exceeded print width in SecureClusterUsingHelmChart. Signed-off-by: Saif Chaudhry <schaudhr@redhat.com>
3e11d5c to
a455f7e
Compare
Summary
SecureClusterUsingOperator.tsx), resolving theTODO ROX-33550comment left by ROX-33119Changes
InitBundles/SecureClusterUsingOperator.tsxInitBundles/SecureClusterUsingHelmChart.tsxCRS/SecureClusterUsingHelmChart.tsxClusterDeployment.tsxTest plan
Screenshots