Many xrefs contain "html" instead of "adoc" because they were copied from openshift.docs.com and not fixed.

Pasting here because I can't attach a file.

openshift-docs • authentication/using-service-accounts-in-applications.adoc:
16
17: * For information about requesting bound service account tokens, see xref:../authentication/bound-service-account-tokens.html#bound-sa-tokens-configuring_bound-service-account-tokens[Configuring bound service account tokens using volume projection]
18
19: * For information about creating a service account token secret, see xref:../nodes/pods/nodes-pods-secrets.html#nodes-pods-secrets-creating-sa_nodes-pods-secrets[Creating a service account token secret].
20

openshift-docs • cicd/gitops/monitoring-argo-cd-custom-resource-workloads.adoc:
21 * The `kube-state-metrics` service is running in your cluster.
22: * Optional: If you are enabling monitoring for an Argo CD instance already present in a user-defined project, ensure that the monitoring is xref:../../monitoring/enabling-monitoring-for-user-defined-projects.html#enabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[enabled for user-defined projects] in your cluster.
23 +

openshift-docs • cicd/pipelines/installing-pipelines.adoc:
52
53: ** xref:../../cicd/pipelines/creating-applications-with-cicd-pipelines.html#op-mirroring-images-to-run-pipelines-in-restricted-environment_creating-applications-with-cicd-pipelines[Mirroring images to run pipelines in a restricted environment]
54

openshift-docs • cicd/pipelines/reducing-pipelines-resource-consumption.adoc:
14
-15: * xref:../../applications/quotas/quotas-setting-per-project.html[Set and manage resource quotas] to limit the aggregate resource consumption.
16: * Use xref:../../nodes/clusters/nodes-cluster-limit-ranges.html[limit ranges to restrict resource consumption] for specific objects, such as pods, images, image streams, and persistent volume claims.
17

openshift-docs • distr_tracing/distr_tracing_install/distr-tracing-deploying-jaeger.adoc:
48 ====
-49: There are two ways to install and use

{DTProductName}

, as part of a service mesh or as a stand alone component. If you have installed

{DTShortName}

as part of

{SMProductName}

, you can perform basic configuration as part of the xref:../../service_mesh/v2x/installing-ossm.adoc#installing-ossm[ServiceMeshControlPlane] but for completely control you should configure a Jaeger CR and then xref:../../service_mesh/v2x/ossm-observability.html#ossm-config-external-jaeger_observability[reference your distributed tracing configuration file in the ServiceMeshControlPlane].-
50

openshift-docs • hardware_enablement/kmm-kernel-module-management.adoc:
65 .Additional resources
66: For information on creating a service account, see xref:https://docs.openshift.com/container-platform/4.12/authentication/understanding-and-creating-service-accounts.html#service-accounts-managing_understanding-service-accounts[Creating] service accounts.
67

openshift-docs • installing/disconnected_install/installing-mirroring-disconnected.adoc:
133 // TODO: This title might need to update per sebastian's PR
134: * xref:../../installing/disconnected_install/installing-mirroring-disconnected.html#oc-mirror-updating-cluster-manifests_installing-mirroring-disconnected[Configuring your cluster to use the resources generated by oc-mirror]
135

openshift-docs • installing/installing_aws/installing-aws-localzone.adoc:
67
68: * xref:../../storage/understanding-persistent-storage.html#pvc-storage-class_understanding-persistent-storage[Storage classes]
69

openshift-docs • installing/installing_aws/installing-aws-user-infra.adoc:
167
-168: * See xref:../../support/troubleshooting/troubleshooting-installations.html#monitoring-installation-progress_troubleshooting-installations[Monitoring installation progress] for details about monitoring the installation, bootstrap, and control plane logs as an

{product-title} installation progresses.-
169

openshift-docs • installing/installing_aws/installing-restricted-networks-aws.adoc:
150
-151: * See xref:../../support/troubleshooting/troubleshooting-installations.html#monitoring-installation-progress_troubleshooting-installations[Monitoring installation progress] for details about monitoring the installation, bootstrap, and control plane logs as an {product-title}

installation progresses.-
152

openshift-docs • installing/installing_bare_metal/installing-bare-metal.adoc:
-116 * See xref:../../post_installation_configuration/enabling-cluster-capabilities.adoc[Enabling cluster capabilities] for more information on enabling cluster capabilities that were disabled prior to installation.
117: * See xref:../../installing/cluster-capabilities.html#explanation_of_capabilities_cluster-capabilities[Optional cluster capabilities in
{product-title}

{product-version}] for more information about the features provided by each capability.-
118

openshift-docs • installing/installing_on_prem_assisted/assisted-installer-preparing-to-install.adoc:
25
26: * xref:../installing_bare_metal_ipi/ipi-install-prerequisites.html#network-requirements-increase-mtu_ipi-install-prerequisites[Increase the network MTU]

openshift-docs • installing/installing_openstack/installing-openstack-nfv-preparing.adoc:
-34 * For either type of deployment:
35: ** xref:../../scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.html#what-huge-pages-do_huge-pages[Configure the Node Tuning Operator with huge pages support].
36 * To complete SR-IOV configuration after you deploy your cluster:
37: ** xref:../../networking/hardware_networks/installing-sriov-operator.html#installing-sr-iov-operator_installing-sriov-operator[Install the SR-IOV Operator].
38: ** xref:../../networking/hardware_networks/configuring-sriov-device.html#nw-sriov-networknodepolicy-object_configuring-sriov-device[Configure your SR-IOV network device].
39 ** xref:../../machine_management/creating_machinesets/creating-machineset-osp.adoc#machineset-yaml-osp-sr-iov_creating-machineset-osp[Create SR-IOV compute machines].-

openshift-docs • installing/installing_openstack/installing-openstack-user-sr-iov-kuryr.adoc:
-77 * To complete SR-IOV configuration for your cluster:
78: ** xref:../../post_installation_configuration/network-configuration.html#networking-osp-preparing-for-sr-iov_post-install-network-configuration[Prepare the cluster for SR-IOV].
79: ** xref:../../scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.html#what-huge-pages-do_huge-pages[Install the performance operator with huge pages support].
80: ** xref:../../networking/hardware_networks/installing-sriov-operator.html#installing-sr-iov-operator_installing-sriov-operator[Install the SR-IOV Operator].
81 * xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].-

openshift-docs • installing/installing_openstack/installing-openstack-user-sr-iov.adoc:
-68 ====
69: After you apply the machine config to the machine pool, you can xref:../../post_installation_configuration/machine-configuration-tasks.html#checking-mco-status_post-install-machine-configuration-tasks[watch the machine config pool status] to see when the machines are available.
70 ====-

-87 == Additional resources
88: * xref:../../scalability_and_performance/cnf-low-latency-tuning.html#cnf-understanding-low-latency_cnf-master[Low latency tuning of OpenShift Container Platform nodes]
89 -

-93 * To complete SR-IOV configuration for your cluster:
94: ** xref:../../scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.html#what-huge-pages-do_huge-pages[Configure huge pages support].
95: ** xref:../../networking/hardware_networks/installing-sriov-operator.html#installing-sr-iov-operator_installing-sriov-operator[Install the SR-IOV Operator].
96: ** xref:../../networking/hardware_networks/configuring-sriov-device.html#nw-sriov-networknodepolicy-object_configuring-sriov-device[Configure your SR-IOV network device].
97 * xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].-

openshift-docs • installing/installing_sno/install-sno-installing-sno.adoc:
-48 * See xref:../../post_installation_configuration/enabling-cluster-capabilities.adoc[Enabling cluster capabilities] for more information about enabling cluster capabilities that were disabled prior to installation.
49: * See xref:../../installing/cluster-capabilities.html#explanation_of_capabilities_cluster-capabilities[Optional cluster capabilities in OpenShift Container Platform {product-title}

 

{product-version}

] for more information about the features provided by each capability.
50-

openshift-docs • installing/installing_vsphere/installing-restricted-networks-installer-provisioned-vsphere.adoc:
-68
69: * xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
70 -

openshift-docs • installing/installing_vsphere/installing-restricted-networks-vsphere.adoc:
-108
109: * xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
110-

openshift-docs • installing/installing_vsphere/installing-vsphere-installer-provisioned-customizations.adoc:
-61
62: * xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
63-

openshift-docs • installing/installing_vsphere/installing-vsphere-installer-provisioned-network-customizations.adoc:
-63
64: * xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
65-

openshift-docs • installing/installing_vsphere/installing-vsphere-network-customizations.adoc:
-96
97: * xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
98-

openshift-docs • installing/installing_vsphere/installing-vsphere.adoc:
-96
97: * xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
98-

openshift-docs • installing/installing_vsphere/preparing-to-install-on-vsphere.adoc:
-28
29: See the xref:../../architecture/architecture-installation.html#installation-process_architecture-installation[Installation process] for more information about installer-provisioned and user-provisioned installation processes.
30-

openshift-docs • logging/cluster-logging-dashboards.adoc:
-29
30: For information on the dashboard charts, see xref:../logging/cluster-logging-dashboards.html#cluster-logging-dashboards-logging_cluster-logging-dashboards[About the OpenShift Logging dashboard] and xref:../logging/cluster-logging-dashboards.html#cluster-logging-dashboards-es_cluster-logging-dashboards[About the Logging/Elastisearch Nodes dashboard].
31-

openshift-docs • logging/cluster-logging-release-notes.adoc:
-974
975: * With this update, you can forward log data to Amazon CloudWatch, which provides application and infrastructure monitoring. For more information, see xref:../logging/cluster-logging-external.html#cluster-logging-collector-log-forward-cloudwatch_cluster-logging-external[Forwarding logs to Amazon CloudWatch]. (link:https://issues.redhat.com/browse/LOG-1173[LOG-1173])
976
977: * With this update, you can forward log data to Loki, a horizontally scalable, highly available, multi-tenant log aggregation system. For more information, see xref:../logging/cluster-logging-external.html#cluster-logging-collector-log-forward-loki_cluster-logging-external[Forwarding logs to Loki]. (link:https://issues.redhat.com/browse/LOG-684[LOG-684])
978
979: * With this update, if you use the Fluentd forward protocol to forward log data over a TLS-encrypted connection, now you can use a password-encrypted private key file and specify the passphrase in the Cluster Log Forwarder configuration. For more information, see xref:../logging/cluster-logging-external.html#cluster-logging-collector-log-forward-fluentd_cluster-logging-external[Forwarding logs using the Fluentd forward protocol]. (link:https://issues.redhat.com/browse/LOG-1525[LOG-1525])
980-

openshift-docs • logging/cluster-logging.adoc:
-34 .Next steps
35: * See xref:../logging/cluster-logging-external.html#cluster-logging-collector-log-forward-cloudwatch_cluster-logging-external[Forwarding logs to Amazon CloudWatch] for instructions.
36 endif::[]-

openshift-docs • modules/builds-docker-strategy.adoc:
-32
33: To prevent the contents of input secrets and config maps from appearing in the build output container images and avoid this removal process altogether, xref:../../cicd/builds/build-strategies.html#builds-using-build-volumes_build-strategies-docker[use build volumes] in your Docker build strategy instead.
34 ====-

openshift-docs • modules/builds-input-secrets-configmaps.adoc:
-9 ====
10: To prevent the contents of input secrets and config maps from appearing in build output container images, use build volumes in your xref:../../cicd/builds/build-strategies.html#builds-using-build-volumes_build-strategies-docker[Docker build] and xref:../../cicd/builds/build-strategies.html#builds-using-build-volumes_build-strategies-s2i[source-to-image build] strategies.
11 ====-

openshift-docs • modules/mirror-registry-release-notes.adoc:
-11
12: For an overview of the mirror registry for Red Hat OpenShift, see xref:../../installing/disconnected_install/installing-mirroring-creating-registry.html#mirror-registry-flags_installing-mirroring-creating-registry[Creating a mirror registry with mirror registry for Red Hat OpenShift].
13-

openshift-docs • modules/ossm-configuring-the-threescale-wasm-auth-module.adoc:
-27 * You must have a 3scale tenant account. See link:https://www.3scale.net/signup[SaaS] or link:https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.11/html-single/installing_3scale/index#install-threescale-on-openshift-guide[3scale] 2.11 On-Premises with a matching service and relevant applications and metrics defined.
28: * If you apply the module to the `<product_page>` microservice in the `bookinfo` namespace, see the xref:../../service_mesh/v1x/prepare-to-deploy-applications-ossm.html#ossm-tutorial-bookinfo-overview_deploying-applications-ossm-v1x[Bookinfo sample application].
29 ** The following example is the YAML format for the custom resource for `threescale-wasm-auth` module.-

openshift-docs • modules/ossm-migrating-to-20.adoc:
-212
213: For information about mTLS, see xref:../../service_mesh/v2x/ossm-security.html#ossm-security-mtls_ossm-security[Enabling mutual Transport Layer Security (mTLS)]
214-

openshift-docs • modules/samples-operator-overview.adoc:
-54 * If the Cluster Samples Operator detects it is on an IPv6 network.
55: * If the xref:../openshift_images/image-configuration.html#images-configuration-parameters_image-configuration[image controller configuration parameters] prevent the creation of image streams by using the default image registry, or by using the image registry specified by the xref:../openshift_images/configuring-samples-operator.html#samples-operator-configuration_configuring-samples-operator[`samplesRegistry` setting].
56-

openshift-docs • monitoring/configuring-the-monitoring-stack.adoc:
-147 * xref:../monitoring/enabling-monitoring-for-user-defined-projects.adoc#enabling-monitoring-for-user-defined-projects[Enabling monitoring for user-defined projects]
148: * See xref:../monitoring/troubleshooting-monitoring-issues.html#determining-why-prometheus-is-consuming-disk-space_troubleshooting-monitoring-issues[Determining why Prometheus is consuming a lot of disk space] for steps to query which metrics have the highest number of scrape samples.
149-

openshift-docs • monitoring/enabling-monitoring-for-user-defined-projects.adoc:
-20 * xref:../monitoring/configuring-the-monitoring-stack.adoc#configuring-the-monitoring-stack[Configuring the monitoring stack]
21: * xref:../monitoring/enabling-monitoring-for-user-defined-projects.html#granting-users-permission-to-configure-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[Granting users permission to configure monitoring for user-defined projects]
22-

openshift-docs • monitoring/troubleshooting-monitoring-issues.adoc:
-26 * See xref:../monitoring/configuring-the-monitoring-stack.adoc#setting-scrape-sample-and-label-limits-for-user-defined-projects_configuring-the-monitoring-stack[Setting a scrape sample limit for user-defined projects] for details on how to set a scrape sample limit and create related alerting rules
27: * xref:../support/getting-support.html#support-submitting-a-case_getting-support[Submitting a support case]-

openshift-docs • nodes/containers/nodes-containers-using.adoc:
-71
72: For information on setting which container runtime to use, see xref:../../post_installation_configuration/machine-configuration-tasks.html#create-a-containerruntimeconfig_post-install-machine-configuration-tasks[Creating a `ContainerRuntimeConfig` CR to edit CRI-O parameters].
73-

openshift-docs • nodes/edge/nodes-edge-remote-workers.adoc:
-33
34: For more information on using these objects in a cluster with remote worker nodes, see xref:../../nodes/edge/nodes-edge-remote-workers.html#nodes-edge-remote-workers-strategies_nodes-edge-remote-workers[About remote worker node strategies].
35-

-37
38: For more information on using these objects in a cluster with remote worker nodes, see xref:../../nodes/edge/nodes-edge-remote-workers.html#nodes-edge-remote-workers-strategies_nodes-edge-remote-workers[About remote worker node strategies].
39-

-59
60: * For more information on replica sets, see xref:../../applications/deployments/what-deployments-are.html#deployments-repliasets_what-deployments-are[ReplicaSets].-
-61
62: * For more information on deployments, see xref:../../applications/deployments/what-deployments-are.html#deployments-kube-deployments_what-deployments-are[Deployments].
63
64: * For more information on replication controllers, see xref:../../applications/deployments/what-deployments-are.html#deployments-replicationcontrollers_what-deployments-are[Replication controllers].
65-

openshift-docs • nodes/nodes/nodes-nodes-resources-cpus.adoc:
-21
22: * For more information on the `systemReserved` and `kubeReserved` parameters, see xref:../../nodes/nodes/nodes-nodes-resources-configuring.html#nodes-nodes-resources-configuring-about_nodes-nodes-resources-configuring[Allocating resources for nodes in an

{product-title} cluster].-

openshift-docs • nodes/pods/nodes-pods-secrets.adoc:
-23
24: * For information about requesting bound service account tokens, see xref:../../authentication/bound-service-account-tokens.html#bound-sa-tokens-configuring_bound-service-account-tokens[Using bound service account tokens]
25
26 : * For information about creating a service account token secret, see xref:../../nodes/pods/nodes-pods-secrets.html#nodes-pods-secrets-creating-sa_nodes-pods-secrets[Creating a service account token secret].-


-43
44: * For information on requesting bound service account tokens, see xref:../../authentication/bound-service-account-tokens.html#bound-sa-tokens-configuring_bound-service-account-tokens[Using bound service account tokens]
45-

openshift-docs • openshift_images/image-configuration.adoc:
-31
32: * For more information about global pull secrets, see xref:../openshift_images/managing_images/using-image-pull-secrets.html#images-update-global-pull-secret_using-image-pull-secrets[Updating the global cluster pull secret].
33-

openshift-docs • openshift_images/samples-operator-alt-registry.adoc:
-19
20: For information on viewing the CRI-O logs to view the image source, see xref:../installing/validating-an-installation.html#viewing-the-image-pull-source_validating-an-installation[Viewing the image pull source].
21-

openshift-docs • operators/admin/olm-adding-operators-to-cluster.adoc:
-96 * xref:../../nodes/scheduling/nodes-scheduler-pod-affinity.adoc#nodes-scheduler-pod-affinity-about_nodes-scheduler-pod-affinity[Understanding pod affinity]
97: * xref:../../nodes/scheduling/nodes-scheduler-node-affinity.html#nodes-scheduler-node-affinity-about_nodes-scheduler-node-affinity[Understanding node affinity]
98 * xref:../../nodes/nodes/nodes-nodes-working.adoc#nodes-nodes-working-updating_nodes-nodes-working[Understanding how to update labels on nodes].-

openshift-docs • post_installation_configuration/cluster-tasks.adoc:
-555
556: * xref:../installing/installing_aws/installing-aws-localzone.html[Installing a cluster using AWS Local Zones]
557-

openshift-docs • post_installation_configuration/storage-configuration.adoc:
-88
89: * xref:../logging/config/cluster-logging-log-store.html#cluster-logging-elasticsearch-storage_cluster-logging-store[Configuring persistent storage for the log store]-

openshift-docs • rosa_release_notes/rosa-release-notes.adoc:
-20
21: * {}ROSA CLI update:{} The ROSA CLI (`rosa`) has been updated to a new version. For information about what's changed in this release, see the link:https://github.com/openshift/rosa/releases/tag/v1.2.23[release] notes. For more information about the ROSA CLI (`rosa`,) see xref:../rosa_cli/rosa-get-started-cli.html[Getting started with the rosa CLI].
22
23: * {}ROSA regional availability update:{} {product-title}

(ROSA) is now available in the United Arab Emirates (`me-central-1`) region. For more information on region availability, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.html#rosa-sdpolicy-regions-az_rosa-service-definition[Regions and availability zones].
24-

openshift-docs • scalability_and_performance/optimization/optimizing-storage.adoc:
-38
39: * xref:../../logging/config/cluster-logging-log-store.html#cluster-logging-elasticsearch-storage_cluster-logging-store[Configuring persistent storage for the log store]-

openshift-docs • scalability_and_performance/recommended-performance-scale-practices/recommended-control-plane-practices.adoc:
-23
24: If you are uncertain about the state of the `ControlPlaneMachineSet` CR in your cluster, you can xref:../../machine_management/control_plane_machine_management/cpmso-getting-started.html#cpmso-checking-status_cpmso-getting-started[verify the CR status].
25 ====-

openshift-docs • scalability_and_performance/ztp_far_edge/ztp-preparing-the-hub-cluster.adoc:
-19
20: * xref:../../scalability_and_performance/cnf-talm-for-cluster-upgrades.html#installing-topology-aware-lifecycle-manager-using-cli_cnf-topology-aware-lifecycle-manager[Installing
{cgu-operator}

]
21-

openshift-docs • sd_support/remote_health_monitoring/about-remote-health-monitoring.adoc:
-78 ifndef::openshift-dedicated,openshift-rosa[]
79: * See xref:../../sd_support/remote_health_monitoring/showing-data-collected-by-remote-health-monitoring.html#insights-operator-showing-data-collected-from-the-cluster_showing-data-collected-by-remote-health-monitoring[Showing data collected by the Insights Operator] for details about how to review the data that is collected by the Insights Operator.
80 endif::[]-

openshift-docs • security/compliance_operator/compliance-operator-understanding.adoc:
-21
22: * xref:../../security/compliance_operator/compliance-operator-supported-profiles.html#compliance-operator-supported-profiles[Supported compliance profiles]-

openshift-docs • security/file_integrity_operator/file-integrity-operator-release-notes.adoc:
-38
39: * The File Integrity Operator is now stable and the release channel is upgraded to `stable`. Future releases will follow link:https://semver.org/[Semantic] Versioning. To access the latest release, see xref:../../security/file_integrity_operator/file-integrity-operator-updating.html#olm-preparing-upgrade_file-integrity-operator-updating[Updating the File Integrity Operator].
40-

openshift-docs • security/security_profiles_operator/spo-seccomp.adoc:
-27 * link:https://cloud.redhat.com/blog/managing-sccs-in-openshift[Managing] SCCs in OpenShift
28: * xref:../../security/security_profiles_operator/spo-advanced.html#spo-log-enricher_spo-advanced[Using the log enricher]
29: * xref:../../security/security_profiles_operator/spo-understanding.html#spo-about_spo-understanding[About security profiles]-

openshift-docs • security/security_profiles_operator/spo-selinux.adoc:
-33 * link:https://cloud.redhat.com/blog/managing-sccs-in-openshift[Managing] SCCs in OpenShift
34: * xref:../../security/security_profiles_operator/spo-advanced.html#spo-log-enricher_spo-advanced[Using the log enricher]
35: * xref:../../security/security_profiles_operator/spo-understanding.html#spo-about_spo-understanding[About security profiles]-

openshift-docs • service_mesh/v1x/ossm-custom-resources.adoc:
-26 ifdef::openshift-enterprise[]
27: Cluster administrators can refer to xref:../../networking/ingress-operator.html#using-wildcard-routes_configuring-ingress[Using wildcard routes] for instructions on how to enable subdomains.
28 endif::[]-

openshift-docs • service_mesh/v2x/prepare-to-deploy-applications-ossm.adoc:
-13 ifdef::openshift-enterprise[]
14: For more information, see the

-{product-title}

documentation, xref:../../applications/deployments/what-deployments-are.html[Understanding Deployment and DeploymentConfig objects].-
15 endif::[]-

openshift-docs • snippets/rosa-hcp-rn.adoc:
-5 :_content-type: SNIPPET
6: * {}Hosted control planes:{} {hcp-title-first} clusters are now available as a link:https://access.redhat.com/support/offerings/techpreview[Technology] Preview feature. This new architecture provides a lower-cost, more resilient ROSA architecture. For more information, see xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.html[Creating \{hcp-title} clusters using the default options].-

openshift-docs • storage/container_storage_interface/ephemeral-storage-shared-resource-csi-driver-operator.adoc:
-42 * xref:../../support/remote_health_monitoring/insights-operator-simple-access.adoc#insights-operator-simple-access[Importing simple content access certificates with Insights Operator]
43: * xref:../../cicd/builds/running-entitled-builds.html#builds-source-secrets-entitlements_running-entitled-builds[Adding subscription entitlements as a build secret]-

openshift-docs • support/remote_health_monitoring/about-remote-health-monitoring.adoc:
-80 ifndef::openshift-dedicated[]
81: * See xref:../../support/remote_health_monitoring/showing-data-collected-by-remote-health-monitoring.html#insights-operator-showing-data-collected-from-the-cluster_showing-data-collected-by-remote-health-monitoring[Showing data collected by the Insights Operator] for details about how to review the data that is collected by the Insights Operator.
82 endif::[]-

openshift-docs • updating/understanding-upgrade-channels-release.adoc:
-52 * xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#update-conditional-upgrade-pathupdating-cluster-cli[Updating along a conditional upgrade path]
53: * xref:../updating/understanding-upgrade-channels-release.html#fast-stable-channel-strategies_{context}[Choosing the correct channel for your cluster]-

openshift-docs • web_console/dynamic-plugin/dynamic-plugins-get-started.adoc:
-8
9: To get started using the dynamic plugin, you must set up your environment to write a new {product-title}

dynamic plugin. For an example of how to write a new plugin, see xref:../../web_console/dynamic-plugin/dynamic-plugin-example.html#adding-tab-to-pods-page_dynamic-plugin-example[Adding a tab to the pods page].
10-

openshift-docs • welcome/index.adoc:
-288
289: - {}xref:../windows_containers/understanding-windows-container-workloads.html#understanding-windows-container-workloads_understanding-windows-container-workloads[Understanding Windows container workloads]{}. You can use the

{productwinc}

feature to run Windows compute nodes in an

{product-title}

cluster. This is possible by using the Red Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes.
290-