remove allinone for k8s and oc sections

user/pages/13.special/01.general/docs.md

@@ -6,7 +6,7 @@ taxonomy:
 
 
 ### Testing NeuVector Using the Allinone Container
-The examples in this section deploy the Allinone and Enforcer containers. This is useful for trying out NeuVector. For production deployments where the Manager, Controller, and Enforcers can all be deployed separately, please see the section Deploying NeuVector.
+The examples in this section deploy the Allinone and Enforcer containers. This is useful for trying out NeuVector, especially on non-Kubernetes (e.g. docker native) environments. For Kubernetes based deployments using the latest NeuVector Helm chart is recommended. Please see the section Deploying NeuVector.
 
 ### General Guidelines for Deployment
 Prepare your host environment for proper installation. Make sure the NeuVector containers can communicate with each other between hosts. Then review and edit the sample files for you environment.
@@ -22,10 +22,8 @@ volumes:
         - /sys/fs/cgroup:/host/cgroup:ro
 ```
 3. Open required ports on hosts. Make sure the required ports are mapped properly and open on the host. The allinone requires 8443 (if using the console), 18300, 18301, 18400, and 18401. The Enforcer requires 18301 and 18401.
-4. (Docker native only) Edit the CLUSTER_JOIN_ADDR. Find the node IP address, node name (if using a name server, or node variable (if using orchestration tools) for the allinone (controller) to use for the “node IP” in the sample files for both allinone and enforcer.
+4. Edit the CLUSTER_JOIN_ADDR. Find the node IP address, node name (if using a name server, or node variable (if using orchestration tools) for the allinone (controller) to use for the “node IP” in the sample files for both allinone and enforcer.
 
-### Helm Deployment
-Automated deployment using helm is available is at https://github.com/neuvector/neuvector-helm.
 
 ### Accessing the Console
 Please see the first section Basics -> Connect to Manager for options for turning off https or accessing the console through a corporate firewall which does not allow port 8443 for the console access.

user/pages/13.special/04.docker/docs.md → user/pages/13.special/02.docker/docs.md

@@ -5,11 +5,8 @@ taxonomy:
 ---
 
 
-### Mirantis Kubernetes Engine
-Deploy to Kubernetes using the [Kubernetes Allinone](/special/kubernetes) section. 
-
 ### Deploy to Swarm Cluster
-It’s simple to deploy NeuVector using a Swarm cluster. First, pull the NeuVector images using Docker UCP in the Images menu. You may need to add a version number to get the latest version on Docker Hub.
+To deploy NeuVector using a Swarm cluster, first pull the NeuVector images using Docker UCP in the Images menu. You may need to add a version number to get the latest version on Docker Hub.
 
 Currently, Swarm/UCP does not support the seccomp capabilities (cap_add options) or deploying in ‘privileged mode’ so the NeuVector containers will need to be deployed from the command line using docker-compose or run. See the sample compose files for the allinone and enforcer below.