Skip to content

OSDOCS-12062: Updating Capabilities table for 4.17 #82183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
obrown1205 wants to merge 1 commit into from
Closed

OSDOCS-12062: Updating Capabilities table for 4.17 #82183

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions snippets/capabilities-table.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,9 @@ The following table describes the `baselineCapabilitySet` values.
|`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`
Copy link
Copy Markdown
Member

@wking wking Sep 23, 2024

Choose a reason for hiding this comment

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

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:

  1. Land this pull with just v4.17 in dev/4.18.
  2. Robot cherry-pick back to 4.17.
  3. Follow-up dev/4.18 pull to add v4.18.

or:

  1. Land a dev/4.18 pull adding both v4.18 and v4.17.
  2. Manual backport to 4.17 that only adds v4.17.

I don't have an opinion on which will be less work for docs.

Copy link
Copy Markdown
Contributor Author

@obrown1205 obrown1205 Oct 21, 2024

Choose a reason for hiding this comment

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

I'll just open it again on enterprise-4.17 :) Thanks!

|Specify this option when you want to enable the default capabilities for {product-title} 4.17. By specifying `v4.17`, capabilities that are introduced in newer versions of {product-title} are not enabled. The default capabilities in {product-title} 4.17 are `baremetal`, `MachineAPI`, `marketplace`, `OperatorLifecycleManager`, `openshift-samples`, `Console`, `Insights`, `Storage`, `CSISnapshot`, `NodeTuning`, `ImageRegistry`, `Build`, `CloudCredential`, `DeploymentConfig`, and `CloudControllerManager`.

|`None`
|Specify when the other sets are too large, and you do not need any capabilities or want to fine-tune via `additionalEnabledCapabilities`.

Expand Down