Skip to content
Merged
Show file tree
Hide file tree
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
8 changes: 4 additions & 4 deletions modules/ossm-rn-new-features.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -1140,8 +1140,8 @@ This release of {SMProductName} adds new features and enhancements, and is suppo
=== `WasmPlugin` API
This release adds support for the `WasmPlugin` API and deprecates the `ServiceMeshExtension` API.

=== ROSA support
This release introduces service mesh support for Red Hat OpenShift on AWS (ROSA), including multi-cluster federation.
=== Red Hat OpenShift Service on AWS support
This release introduces service mesh support for Red Hat OpenShift Service on AWS, including multi-cluster federation.

=== `istio-node` DaemonSet renamed
This release, the `istio-node` DaemonSet is renamed to `istio-cni-node` to match the name in upstream Istio.
Expand Down Expand Up @@ -1485,10 +1485,10 @@ New Custom Resource Definitions (CRDs) have been added to support federating ser
* `ImportedServiceSet` - Defines which services for a given `ServiceMeshPeer` are imported from the peer mesh. These services must also be made available by the peer’s `ExportedServiceMeshSet` resource.

ifndef::openshift-rosa-hcp,openshift-rosa[]
Service Mesh Federation is not supported between clusters on Red Hat OpenShift Service on AWS (ROSA), Azure Red Hat OpenShift (ARO), or OpenShift Dedicated (OSD).
Service Mesh Federation is not supported between clusters on Red Hat OpenShift Service on AWS, Azure Red Hat OpenShift (ARO), or OpenShift Dedicated.
endif::openshift-rosa-hcp,openshift-rosa[]
ifdef::openshift-rosa-hcp,openshift-rosa[]
Service Mesh Federation is not supported between clusters on Red Hat OpenShift Service on AWS (ROSA) or OpenShift Dedicated (OSD).
Service Mesh Federation is not supported between clusters on Red Hat OpenShift Service on AWS or OpenShift Dedicated.
endif::openshift-rosa-hcp,openshift-rosa[]

=== OVN-Kubernetes Container Network Interface (CNI) generally available
Expand Down
2 changes: 1 addition & 1 deletion nodes/clusters/nodes-containers-events.adoc
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
:_mod-docs-content-type: ASSEMBLY
:context: nodes-containers-events
[id="nodes-containers-events"]
= Viewing system event information in an {product-title} cluster
= Viewing system event information in {product-title} clusters
include::_attributes/common-attributes.adoc[]

toc::[]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -183,9 +183,9 @@ Before installing this version of the Custom Metrics Autoscaler Operator, remove
=== New features and enhancements

[id="nodes-pods-autoscaling-custom-rn-2112-new-rosa-osd_{context}"]
==== Red Hat OpenShift Service on AWS (ROSA) and OpenShift Dedicated are now supported
==== Red Hat OpenShift Service on AWS and OpenShift Dedicated are now supported

The Custom Metrics Autoscaler Operator 2.11.2-311 can be installed on OpenShift ROSA and OpenShift Dedicated managed clusters. Previous versions of the Custom Metrics Autoscaler Operator could be installed only in the `openshift-keda` namespace. This prevented the Operator from being installed on OpenShift ROSA and OpenShift Dedicated clusters. This version of Custom Metrics Autoscaler allows installation to other namespaces such as `openshift-operators` or `keda`, enabling installation into ROSA and Dedicated clusters.
The Custom Metrics Autoscaler Operator 2.11.2-311 can be installed on Red Hat OpenShift Service on AWS and OpenShift Dedicated managed clusters. Previous versions of the Custom Metrics Autoscaler Operator could be installed only in the `openshift-keda` namespace. This prevented the Operator from being installed on Red Hat OpenShift Service on AWS and OpenShift Dedicated clusters. This version of Custom Metrics Autoscaler allows installation to other namespaces such as `openshift-operators` or `keda`, enabling installation into Red Hat OpenShift Service on AWS and OpenShift Dedicated clusters.

[id="nodes-pods-autoscaling-custom-rn-2112-bugs_{context}"]
=== Bug fixes
Expand Down
2 changes: 1 addition & 1 deletion nodes/containers/nodes-containers-copying-files.adoc
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
:_mod-docs-content-type: ASSEMBLY
:context: nodes-containers-copying-files
[id="nodes-containers-copying-files"]
= Copying files to or from an {product-title} container
= Copying files to or from {product-title} containers
include::_attributes/common-attributes.adoc[]

toc::[]
Expand Down
2 changes: 1 addition & 1 deletion nodes/containers/nodes-containers-remote-commands.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ toc::[]



You can use the CLI to execute remote commands in an {product-title} container.
You can use the CLI to execute remote commands in {product-title} containers.

// The following include statements pull in the module files that comprise
// the assembly. Include any combination of concept, procedure, or reference
Expand Down
8 changes: 7 additions & 1 deletion nodes/jobs/nodes-pods-daemonsets.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,13 @@ include::_attributes/common-attributes.adoc[]

toc::[]

As an administrator, you can create and use daemon sets to run replicas of a pod on specific or all nodes in an {product-title} cluster.
As an administrator, you can create and use daemon sets to run replicas of a pod on specific or all nodes in
ifndef::openshift-rosa,openshift-rosa-hcp[]
an {product-title} cluster.
endif::openshift-rosa,openshift-rosa-hcp[]
ifdef::openshift-rosa,openshift-rosa-hcp[]
a {product-title} cluster.
endif::openshift-rosa,openshift-rosa-hcp[]

A daemon set ensures that all (or some) nodes run a copy of a pod. As nodes are added to the cluster, pods are added to the cluster.
As nodes are removed from the cluster, those pods are removed through garbage collection. Deleting a daemon set will clean up the pods it created.
Expand Down