OSDOCS-12062: Updating Capabilities table for 4.17#82183
OSDOCS-12062: Updating Capabilities table for 4.17#82183obrown1205 wants to merge 1 commit intoopenshift:mainfrom
Conversation
|
@obrown1205: This pull request references OSDOCS-12062 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.18.0" version, but no target version was set. 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. |
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
Bot
added
the
size/XS
|
🤖 Thu Sep 19 16:30:29 - Prow CI generated the docs preview: |
|
@obrown1205: 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. |
|
@obrown1205: This pull request references OSDOCS-12062 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.18.0" version, but no target version was set. 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. |
| |`v4.16` | ||
| |Specify this option when you want to enable the default capabilities for {product-title} 4.16. By specifying `v4.16`, capabilities that are introduced in newer versions of {product-title} are not enabled. The default capabilities in {product-title} 4.16 are `baremetal`, `MachineAPI`, `marketplace`, `OperatorLifecycleManager`, `openshift-samples`, `Console`, `Insights`, `Storage`, `CSISnapshot`, `NodeTuning`, `ImageRegistry`, `Build`, `CloudCredential`, `DeploymentConfig`, and `CloudControllerManager`. | ||
|
|
||
| |`v4.17` |
There was a problem hiding this comment.
The dev-branch/4.18 will want v4.18 too (openshift/api#2022) but the 4.17 backport only needs v4.17 (openshift/api#2023). I dunno how you want to structure that in docs. Could be either:
- Land this pull with just
v4.17in dev/4.18. - Robot cherry-pick back to 4.17.
- Follow-up dev/4.18 pull to add
v4.18.
or:
- Land a dev/4.18 pull adding both
v4.18andv4.17. - Manual backport to 4.17 that only adds
v4.17.
I don't have an opinion on which will be less work for docs.
There was a problem hiding this comment.
I'll just open it again on enterprise-4.17 :) Thanks!
4 participants
Version(s):
4.17+
Issue:
OSDOCS-12062
for OCPBUGS-41642
Link to docs preview:
https://82183--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/overview/cluster-capabilities.html
QE review:
Additional information: