Telcodocs-230 Updating Performing end-to-end tests for platform verification

Author: kquinn1204

modules/cnf-performing-end-to-end-tests-for-platform-verification.adoc

@@ -23,6 +23,7 @@ Validations include:
 * Having the Performance Addon Operator installed
 * Having the SR-IOV Operator installed
 * Having the PTP Operator installed
+* Enabling the `contain-mount-namespace` mode via machine config
 * Using OVN kubernetes as the SDN
 
 Latency tests, a part of the CNF-test container, also require the same validations. For more information about running a latency test, see the Running the latency tests section.
@@ -211,6 +212,7 @@ The set of available features to filter are:
 * `sctp`
 * `xt_u32`
 * `dpdk`
+* `container-mount-namespace`
 
 [id="cnf-performing-end-to-end-tests-dry-run_{context}"]
 == Dry run
@@ -430,6 +432,10 @@ Various tests have different requirements. Some of them are:
 * A performance profile having `profile.Spec.RealTimeKernel.Enabled == true`.
 * A node with no huge pages usage.
 
+.Container-mount-namespace tests
+
+* A node with a machine config which enables `container-mount-namespace` mode
+
 [id="limiting-nodes-used-during-tests_{context}"]
 === Limiting the nodes used during tests
 
@@ -626,6 +632,11 @@ Performance tests apply a performance profile to the cluster. The effect of this
 
 DPDK relies on both performance and SR-IOV features, so the test suite configures both a performance profile and SR-IOV networks, so the impacts are the same as those described in SR-IOV testing and performance testing.
 
+[id="cnf-performing-end-to-end-tests-container-mount-namespace_{context}"]
+=== Container-mount-namespace
+
+The validation test for `container-mount-namespace` mode only checks that the appropriate `MachineConfig` objects are present and active, and has no additional impact on the node.
+
 [id="cnf-performing-end-to-end-tests-cleaning-up_{context}"]
 === Cleaning up