openshift · xenolinux · Oct 30, 2025 · Oct 28, 2025
diff --git a/modules/kube-apiserver-operator.adoc b/modules/kube-apiserver-operator.adoc
@@ -2,6 +2,7 @@
 //
 // * operators/operator-reference.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="kube-apiserver-operator_{context}"]
 = Kubernetes API Server Operator
 

diff --git a/modules/kube-controller-manager-operator.adoc b/modules/kube-controller-manager-operator.adoc
@@ -2,6 +2,7 @@
 //
 // * operators/operator-reference.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="kube-controller-manager-operator_{context}"]
 = Kubernetes Controller Manager Operator
 

diff --git a/modules/ldap-syncing-examples.adoc b/modules/ldap-syncing-examples.adoc
@@ -2,17 +2,14 @@
 //
 // * authentication/ldap-syncing.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="ldap-syncing-examples_{context}"]
 = LDAP group sync examples
 
-This section contains examples for the RFC 2307, Active Directory, and
-augmented Active Directory schemas.
+This section contains examples for the RFC 2307, Active Directory, and augmented Active Directory schemas.
 
 [NOTE]
 ====
-These examples assume that all users are direct members of their respective
-groups. Specifically, no groups have other groups as members. See
-the Nested Membership Sync Example for information on
-how to sync nested groups.
+These examples assume that all users are direct members of their respective groups. Specifically, no groups have other groups as members. See the Nested Membership Sync Example for information on how to sync nested groups.
 ====
 
diff --git a/modules/ldap-syncing-pruning.adoc b/modules/ldap-syncing-pruning.adoc
@@ -2,13 +2,11 @@
 //
 // * authentication/ldap-syncing.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="ldap-syncing-pruning_{context}"]
 = Running a group pruning job
 
-An administrator can also choose to remove groups from {product-title} records
-if the records on the LDAP server that created them are no longer present. The
-prune job will accept the same sync configuration file and whitelists or blacklists
-as used for the sync job.
+An administrator can also choose to remove groups from {product-title} records if the records on the LDAP server that created them are no longer present. The prune job will accept the same sync configuration file and whitelists or blacklists as used for the sync job.
 
 For example:
 

diff --git a/modules/ldap-syncing-running.adoc b/modules/ldap-syncing-running.adoc
@@ -2,6 +2,7 @@
 //
 // * authentication/ldap-syncing-groups.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="ldap-syncing-running_{context}"]
 = Running LDAP sync
 

diff --git a/modules/ldap-syncing-spec.adoc b/modules/ldap-syncing-spec.adoc
@@ -2,6 +2,7 @@
 //
 // * authentication/ldap-syncing.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="ldap-syncing-spec_{context}"]
 = LDAP sync configuration specification
 

diff --git a/modules/log-verbosity-descriptions.adoc b/modules/log-verbosity-descriptions.adoc
@@ -1,3 +1,8 @@
+// Module included in the following assemblies:
+//
+//rest_api/overview/editing-kubelet-log-level-verbosity.adoc
+
+:_mod-docs-content-type: REFERENCE
 [id="log-verbosity-descriptions_{context}"]
 = Log verbosity descriptions
 

diff --git a/modules/logging-into-a-cluster-after-installation.adoc b/modules/logging-into-a-cluster-after-installation.adoc
@@ -2,6 +2,7 @@
 //
 // *installing/validation_and_troubleshooting/validating-an-installation.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="logging-into-a-cluster-after-installation_{context}"]
 = Logging into a cluster after an installation
 

diff --git a/modules/machine-api-operator.adoc b/modules/machine-api-operator.adoc
@@ -2,6 +2,7 @@
 //
 // * operators/operator-reference.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="machine-api-operator_{context}"]
 = Machine API Operator
 

diff --git a/modules/machine-config-daemon-metrics-understanding.adoc b/modules/machine-config-daemon-metrics-understanding.adoc
@@ -2,6 +2,7 @@
 //
 // * machine-config/machine-config-daemon-metrics.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="machine-config-daemon-metrics-understanding_{context}"]
 = Understanding Machine Config Daemon metrics
 

diff --git a/modules/machine-config-operator.adoc b/modules/machine-config-operator.adoc
@@ -2,6 +2,7 @@
 //
 // * operators/operator-reference.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="machine-config-operator_{context}"]
 = Machine Config Operator
 

diff --git a/modules/machine-health-checks-resource.adoc b/modules/machine-health-checks-resource.adoc
@@ -3,7 +3,7 @@
 // * machine_management/deploying-machine-health-checks.adoc
 // * post_installation_configuration/node-tasks.adoc
 
-
+:_mod-docs-content-type: CONCEPT
 [id="machine-health-checks-resource_{context}"]
 = Sample MachineHealthCheck resource
 
@@ -61,9 +61,9 @@ The appropriate `maxUnhealthy` value depends on the scale of the cluster you dep
 
 [IMPORTANT]
 ====
-If you configure a `MachineHealthCheck` resource for the control plane, set the value of `maxUnhealthy` to `1`. 
+If you configure a `MachineHealthCheck` resource for the control plane, set the value of `maxUnhealthy` to `1`.
 
-This configuration ensures that the machine health check takes no action when multiple control plane machines appear to be unhealthy. Multiple unhealthy control plane machines can indicate that the etcd cluster is degraded or that a scaling operation to replace a failed machine is in progress. 
+This configuration ensures that the machine health check takes no action when multiple control plane machines appear to be unhealthy. Multiple unhealthy control plane machines can indicate that the etcd cluster is degraded or that a scaling operation to replace a failed machine is in progress.
 
 If the etcd cluster is degraded, manual intervention might be required. If a scaling operation is in progress, the machine health check should allow it to finish.
 ====

diff --git a/modules/machineset-azure-accelerated-networking.adoc b/modules/machineset-azure-accelerated-networking.adoc
@@ -10,6 +10,7 @@ ifeval::["{context}" == "cpmso-config-options-azure"]
 :cpmso:
 endif::[]
 
+:_mod-docs-content-type: REFERENCE
 [id="machineset-azure-accelerated-networking_{context}"]
 = Accelerated Networking for Microsoft Azure VMs
 

diff --git a/modules/machineset-azure-ephemeral-os.adoc b/modules/machineset-azure-ephemeral-os.adoc
@@ -2,6 +2,7 @@
 //
 // * machine_management/creating_machinesets/creating-machineset-azure.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="machineset-azure-ephemeral-os_{context}"]
 = Machine sets that deploy machines on Ephemeral OS disks
 

diff --git a/modules/machineset-dedicated-instances.adoc b/modules/machineset-dedicated-instances.adoc
@@ -3,6 +3,7 @@
 // * machine_management/creating_machinesets/creating-machineset-aws.adoc
 // * machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="machineset-dedicated-instance_{context}"]
 = Machine sets that deploy machines as Dedicated Instances
 

diff --git a/modules/machineset-delete-policy.adoc b/modules/machineset-delete-policy.adoc
@@ -3,6 +3,7 @@
 // * machine_management/manually-scaling-machineset.adoc
 // * post_installation_configuration/cluster-tasks.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="machineset-delete-policy_{context}"]
 = The compute machine set deletion policy
 

diff --git a/modules/machineset-non-guaranteed-instance.adoc b/modules/machineset-non-guaranteed-instance.adoc
@@ -14,6 +14,7 @@ ifeval::["{context}" == "creating-machineset-gcp"]
 :gcp:
 endif::[]
 
+:_mod-docs-content-type: CONCEPT
 [id="machineset-non-guaranteed-instance_{context}"]
 ifdef::aws[= Machine sets that deploy machines as Spot Instances]
 ifdef::azure[= Machine sets that deploy machines as Spot VMs]

diff --git a/modules/machineset-vsphere-required-permissions.adoc b/modules/machineset-vsphere-required-permissions.adoc
@@ -2,6 +2,7 @@
 //
 // * installing/installing_vsphere/installing-restricted-networks-vsphere.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="machineset-vsphere-requirements-user-provisioned-machine-sets_{context}"]
 = Minimum required vCenter privileges for compute machine set management
 

diff --git a/modules/machineset-yaml-osp-sr-iov-port-security.adoc b/modules/machineset-yaml-osp-sr-iov-port-security.adoc
@@ -2,6 +2,7 @@
 //
 // * machine_management/creating_machinesets/creating-machineset-osp.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="machineset-yaml-osp-sr-iov-port-security_{context}"]
 =  Sample YAML for SR-IOV deployments where port security is disabled
 

diff --git a/modules/machineset-yaml-osp-sr-iov.adoc b/modules/machineset-yaml-osp-sr-iov.adoc
@@ -2,6 +2,7 @@
 //
 // * machine_management/creating_machinesets/creating-machineset-osp.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="machineset-yaml-osp-sr-iov_{context}"]
 =  Sample YAML for a compute machine set custom resource that uses SR-IOV on {rh-openstack}
 
@@ -91,7 +92,7 @@ spec:
           userDataSecret:
             name: <node_role>-user-data
           availabilityZone: <optional_openstack_availability_zone>
-          configDrive: true <5> 
+          configDrive: true <5>
 ----
 <1> Enter a network UUID for each port.
 <2> Enter a subnet UUID for each port.

diff --git a/modules/maintaining-bare-metal-hosts.adoc b/modules/maintaining-bare-metal-hosts.adoc
@@ -2,6 +2,7 @@
 //
 // scalability_and_performance/managing-bare-metal-hosts.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="maintaining-bare-metal-hosts_{context}"]
 = Maintaining bare metal hosts
 

diff --git a/modules/master-node-sizing.adoc b/modules/master-node-sizing.adoc
@@ -3,6 +3,7 @@
 // * scalability_and_performance/recommended-performance-scale-practices/recommended-control-plane-practices.adoc
 // * post_installation_configuration/node-tasks.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="master-node-sizing_{context}"]
 =  Control plane node sizing
 

diff --git a/modules/migration-direct-volume-migration-and-direct-image-migration.adoc b/modules/migration-direct-volume-migration-and-direct-image-migration.adoc
@@ -3,6 +3,7 @@
 // * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
 // * migration_toolkit_for_containers/migrating-applications-with-mtc.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="migration-direct-volume-migration-and-direct-image-migration_{context}"]
 = Direct volume migration and direct image migration
 

diff --git a/modules/migration-hooks.adoc b/modules/migration-hooks.adoc
@@ -3,6 +3,7 @@
 // * migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc
 // * migration_toolkit_for_containers/advanced-migration-options-mtc.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="migration-hooks_{context}"]
 = Migration hooks
 

diff --git a/modules/migration-known-issues.adoc b/modules/migration-known-issues.adoc
@@ -3,6 +3,7 @@
 // * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
 // * migration_toolkit_for_containers/troubleshooting-mtc
 
+:_mod-docs-content-type: CONCEPT
 [id="migration-known-issues_{context}"]
 = Known issues
 

diff --git a/modules/migration-mapping-destination-namespaces-in-the-migplan-cr.adoc b/modules/migration-mapping-destination-namespaces-in-the-migplan-cr.adoc
@@ -2,6 +2,7 @@
 //
 // * migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="migration-mapping-destination-namespaces-in-the-migplan-cr_{context}"]
 = Mapping namespaces
 

diff --git a/modules/migration-mtc-cr-manifests.adoc b/modules/migration-mtc-cr-manifests.adoc
@@ -3,6 +3,7 @@
 // * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
 // * migration_toolkit_for_containers/migrating-applications-with-mtc
 
+:_mod-docs-content-type: CONCEPT
 [id="migration-mtc-cr-manifests_{context}"]
 = {mtc-full} custom resource manifests
 

diff --git a/modules/migration-mtc-workflow.adoc b/modules/migration-mtc-workflow.adoc
@@ -5,6 +5,7 @@
 // * migration_toolkit_for_containers/about-mtc.adoc
 // * migration_toolkit_for_containers/advanced-migration-options-mtc.adoc
 
+:_mod-docs-content-type: PROCEDURE
 [id="migration-mtc-workflow_{context}"]
 = {mtc-short} workflow
 

diff --git a/modules/migration-network-traffic-redirection-strategies.adoc b/modules/migration-network-traffic-redirection-strategies.adoc
@@ -3,6 +3,7 @@
 // * migrating_from_ocp_3_to_4/planning-considerations-3-4.adoc
 // * migration_toolkit_for_containers/network-considerations-mtc.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="migration-network-traffic-redirection-strategies_{context}"]
 = Network traffic redirection strategies
 

diff --git a/modules/migration-prerequisites.adoc b/modules/migration-prerequisites.adoc
@@ -5,6 +5,7 @@
 // * migration_toolkit_for_containers/migrating-applications-with-mtc
 // * migration_toolkit_for_containers/advanced-migration-options-mtc.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="migration-prerequisites_{context}"]
 = Migration prerequisites
 

diff --git a/modules/migration-provided-metrics.adoc b/modules/migration-provided-metrics.adoc
@@ -3,6 +3,7 @@
 // * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
 // * migration-toolkit-for-containers/troubleshooting-mtc.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="migration-provided-metrics_{context}"]
 = Provided metrics
 

diff --git a/modules/migration-terminology.adoc b/modules/migration-terminology.adoc
@@ -5,6 +5,7 @@
 // * migration_toolkit_for_containers/about-mtc.adoc
 // * migration_toolkit_for_containers/advanced-migration-options-mtc.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="migration-terminology_{context}"]
 = Terminology
 

diff --git a/modules/migration-writing-ansible-playbook-hook.adoc b/modules/migration-writing-ansible-playbook-hook.adoc
@@ -3,6 +3,7 @@
 // * migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc
 // * migration_toolkit_for_containers/advanced-migration-options-mtc.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="migration-writing-ansible-playbook-hook_{context}"]
 = Writing an Ansible playbook for a migration hook
 

diff --git a/modules/minimum-required-permissions-upi-azure.adoc b/modules/minimum-required-permissions-upi-azure.adoc
@@ -3,6 +3,7 @@
 // * installing/installing_azure/installing-azure-user-infra.adoc
 // * installing/installing_azure/installing-restricted-networks-azure-user-provisioned.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="minimum-required-permissions-upi-azure_{context}"]
 = Required Azure permissions for user-provisioned infrastructure
 

diff --git a/modules/minimum-required-permissions-upi-gcp.adoc b/modules/minimum-required-permissions-upi-gcp.adoc
@@ -4,6 +4,7 @@
 // * installing/installing_gcp/installing-restricted-networks-gcp.adoc
 // * installing/installing_gcp/installing-gcp-user-infra-vpc.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="minimum-required-permissions-upi-gcp_{context}"]
 = Required {gcp-short} permissions for user-provisioned infrastructure
 

diff --git a/modules/nbde-deciding-the-number-of-tang-servers-to-use.adoc b/modules/nbde-deciding-the-number-of-tang-servers-to-use.adoc
@@ -2,6 +2,7 @@
 //
 // security/nbde-implementation-guide.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="nbde-deciding-the-number-of-tang-servers-to-use_{context}"]
 = Tang server sizing requirements
 

diff --git a/modules/nbde-disk-encryption-technology-comparison.adoc b/modules/nbde-disk-encryption-technology-comparison.adoc
@@ -2,6 +2,7 @@
 //
 // security/nbde-implementation-guide.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="nbde-disk-encryption-technology-comparison_{context}"]
 = Disk encryption technology comparison
 

diff --git a/modules/nbde-emergency-recovery-of-network-connectivity.adoc b/modules/nbde-emergency-recovery-of-network-connectivity.adoc
@@ -2,6 +2,7 @@
 //
 // security/nbde-implementation-guide.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="nbde-emergency-recovery-of-network-connectivity_{context}"]
 = Emergency recovery of network connectivity
 

diff --git a/modules/nbde-http-versus-https.adoc b/modules/nbde-http-versus-https.adoc
@@ -2,10 +2,11 @@
 //
 // security/nbde-implementation-guide.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="nbde-http-versus-https_{context}"]
 = HTTP versus HTTPS
 
-Traffic to the Tang server can be encrypted (HTTPS) or plaintext (HTTP). There are no significant security advantages of encrypting this traffic, and leaving it decrypted removes any complexity or failure conditions related to Transport Layer Security (TLS) certificate checking in the node running a Clevis client.
+Traffic to the Tang server can be encrypted (HTTPS) or plain text (HTTP). There are no significant security advantages of encrypting this traffic, and leaving it decrypted removes any complexity or failure conditions related to Transport Layer Security (TLS) certificate checking in the node running a Clevis client.
 
 While it is possible to perform passive monitoring of unencrypted traffic between the node’s Clevis client and the Tang server, the ability to use this traffic to determine the key material is at best a future theoretical concern. Any such traffic analysis would require large quantities of captured data. Key rotation would immediately invalidate it. Finally, any threat actor able to perform passive monitoring has already obtained the necessary network access to perform manual connections to the Tang server and can perform the simpler manual decryption of captured Clevis headers.
 

diff --git a/modules/nbde-installation-scenarios.adoc b/modules/nbde-installation-scenarios.adoc
@@ -2,6 +2,7 @@
 //
 // security/nbde-implementation-guide.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="nbde-installation-scenarios_{context}"]
 = Installation scenarios
 

diff --git a/modules/nbde-key-escrow.adoc b/modules/nbde-key-escrow.adoc
@@ -2,6 +2,7 @@
 //
 // security/nbde-implementation-guide.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="nbde-key-escrow_{context}"]
 = Key escrow
 

diff --git a/modules/nbde-locating-the-tang-servers.adoc b/modules/nbde-locating-the-tang-servers.adoc
@@ -2,6 +2,7 @@
 //
 // security/nbde-implementation-guide.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="nbde-locating-the-tang-servers_{context}"]
 = Tang server location planning
 

diff --git a/modules/nbde-logging-considerations.adoc b/modules/nbde-logging-considerations.adoc
@@ -2,6 +2,7 @@
 //
 // security/nbde-implementation-guide.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="nbde-logging-considerations_{context}"]
 = Logging considerations