Skip to content

Commit a5bb17e

Browse files
authored
Merge pull request #59010 from subhtk/ocpbug10401
OCPBUG10401: Added Notes related to baselineCapabilitySet
2 parents 2288824 + db0ac44 commit a5bb17e

File tree

1 file changed

+13
-2
lines changed

1 file changed

+13
-2
lines changed

modules/selecting-cluster-capabilities.adoc

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,22 @@ During a customized installation, you create an `install-config.yaml` file that
1212
[source,yaml]
1313
----
1414
capabilities:
15-
baselineCapabilitySet: v4.13 <1>
15+
baselineCapabilitySet: v4.11 <1>
1616
additionalEnabledCapabilities: <2>
1717
- CSISnapshot
1818
- Console
1919
- Storage
2020
----
21-
<1> Defines a baseline set of capabilities to install. Valid values are `None`, `v4.12`, `v4.13`, and `vCurrent`. If you select `None`, all optional capabilities will be disabled. The default value is `vCurrent`, which enables all optional capabilities.
21+
<1> Defines a baseline set of capabilities to install. Valid values are `None`, `vCurrent` and `v4.x`. If you select `None`, all optional capabilities will be disabled. The default value is `vCurrent`, which enables all optional capabilities.
22+
+
23+
[NOTE]
24+
====
25+
`v4.x` refers to any value up to and including the current cluster version.
26+
For example, valid values for a {product-title} 4.12 cluster are `v4.11` and `v4.12`.
27+
====
2228
<2> Defines a list of capabilities to explicitly enable. These will be enabled in addition to the capabilities specified in `baselineCapabilitySet`.
29+
+
30+
[NOTE]
31+
====
32+
In this example, the default capability is set to `v4.11`. The `additionalEnabledCapabilities` field enables additional capabilities over the default `v4.11` capability set.
33+
====

0 commit comments

Comments
 (0)