Skip to content
Merged
Changes from all commits
Commits
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
6 changes: 4 additions & 2 deletions release_notes/ocp-4-6-release-notes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ Ignition snippets, they should be created using Ignition spec v3. However, the
Machine Config Operator (MCO) still supports Ignition spec v2.

[id="ocp-4-6-extensions-supported-for-rhcos-mco"]
==== Extensions now supported for {op-system} and MCO
==== Extensions now supported for {op-system} and MCO

{op-system} and the MCO now support the following extensions to the default
{op-system} installation.
Expand Down Expand Up @@ -213,7 +213,7 @@ If the `credentialsMode` field is set to any of the three modes, the
installation program does not check the credential for proper permissions prior
to installing {product-title}. This is useful for when the supplied user
credentials cannot be properly validated due to limitations in the cloud policy
simulator.
simulator.

// For more information on these modes, see operators/operator-reference.adoc#cloud-credential-operator_red-hat-operators[Cloud Credential Operator].

Expand Down Expand Up @@ -470,6 +470,8 @@ The Local Storage Operator now has the ability to:
* Automatically discover a list of available disks in a cluster. You can select a list of nodes, or all nodes, for auto-discovery to be continuously applied to.
* Automatically provision local persistent volumes from attached devices. Appropriate devices are filtered and persistent volumes are provisioned based on the filtered devices.

For more information, see xref:../storage/persistent_storage/persistent-storage-local.adoc#local-storage-discovery_persistent-storage-local[Automating discovery and provisioning for local storage devices].

[id="ocp-4-6-operators"]
=== Operators

Expand Down