diff --git a/modules/nw-sriov-additional-network.adoc b/modules/nw-sriov-additional-network.adoc index 20011baf5653..3367626a1320 100644 --- a/modules/nw-sriov-additional-network.adoc +++ b/modules/nw-sriov-additional-network.adoc @@ -75,7 +75,7 @@ You must enclose the value you specify in quotes or the CR is rejected by the SR + [NOTE] ==== -Intel NICs do not support the `minTxRate` parameter. For more information, see link:https://bugzilla.redhat.com/show_bug.cgi?id=1772847[BZ#1772847]. +Intel NICs do not support the `minTxRate` parameter. For more information, see "BZ#1772847". ==== ** `spec.vlanQoS` an optional field that defines the IEEE 802.1p priority level for the VF. The default value is `0`. ** `spec.trust` an optional field that defines the trust mode of the VF. The allowed values are the strings `"on"` and `"off"`. diff --git a/modules/virt-cluster-ha-options.adoc b/modules/virt-cluster-ha-options.adoc index 788eca9f5c6c..06c0d860a5ee 100644 --- a/modules/virt-cluster-ha-options.adoc +++ b/modules/virt-cluster-ha-options.adoc @@ -20,11 +20,11 @@ In {product-title} clusters installed using installer-provisioned infrastructure Currently, installer-provisioned infrastructure is not supported on {ibm-z-name}. ==== -* Automatic high availability for both IPI and non-IPI is available by using the *Node Health Check Operator* on the {product-title} cluster to deploy the `NodeHealthCheck` controller. The controller identifies unhealthy nodes and uses a remediation provider, such as the Self Node Remediation Operator or Fence Agents Remediation Operator, to remediate the unhealthy nodes. For more information on remediation, fencing, and maintaining nodes, see the link:https://access.redhat.com/documentation/en-us/workload_availability_for_red_hat_openshift[Workload Availability for Red Hat OpenShift] documentation. +* Automatic high availability for both IPI and non-IPI is available by using the *Node Health Check Operator* on the {product-title} cluster to deploy the `NodeHealthCheck` controller. The controller identifies unhealthy nodes and uses a remediation provider, such as the Self Node Remediation Operator or Fence Agents Remediation Operator, to remediate the unhealthy nodes. For more information on remediation, fencing, and maintaining nodes, see the "Workload Availability for Red Hat OpenShift" documentation. + [NOTE] ==== -Fence Agents Remediation uses supported fencing agents to reset failed nodes faster than the Self Node Remediation Operator. This improves overall virtual machine high availability. For more information, see the link:https://access.redhat.com/articles/7057929[{VirtProductName} - Fencing and VM High Availability Guide] knowledgebase article. +Fence Agents Remediation uses supported fencing agents to reset failed nodes faster than the Self Node Remediation Operator. This improves overall virtual machine high availability. For more information, see the "{VirtProductName} - Fencing and VM High Availability Guide" knowledgebase article. ==== * High availability for any platform is available by using either a monitoring system or a qualified human to monitor node availability. When a node is lost, shut it down and run `oc delete node `. diff --git a/modules/virt-networking-glossary.adoc b/modules/virt-networking-glossary.adoc index 581e73a29e8f..c5b20c6c29d2 100644 --- a/modules/virt-networking-glossary.adoc +++ b/modules/virt-networking-glossary.adoc @@ -10,7 +10,7 @@ [role="_abstract"] The following terms are used throughout {VirtProductName} documentation. -Container Network Interface (CNI):: A link:https://www.cncf.io/[Cloud Native Computing Foundation] +Container Network Interface (CNI):: A Cloud Native Computing Foundation project, focused on container network connectivity. {VirtProductName} uses CNI plugins to build upon the basic Kubernetes networking functionality. @@ -18,7 +18,7 @@ ifndef::openshift-dedicated[] Multus:: A "meta" CNI plugin that allows multiple CNIs to exist so that a pod or virtual machine can use the interfaces it needs. endif::openshift-dedicated[] -Custom resource definition (CRD):: A link:https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/[Kubernetes] +Custom resource definition (CRD):: A Kubernetes API resource that allows you to define custom resources, or an object defined by using the CRD API resource. `NetworkAttachmentDefinition`:: A CRD introduced by the Multus project that allows you to attach pods, virtual machines, and virtual machine instances to one or more networks.