General Guidelines
Testing SUSE® Security Using the Allinone Container
The examples in this section deploy the Allinone and Enforcer containers. This is useful for trying out SUSE® Security, especially on non-Kubernetes (e.g. docker native) environments. For Kubernetes based deployments using the latest SUSE® Security Helm chart is recommended. Please see the section Deploying SUSE® Security.
General Guidelines for Deployment
Prepare your host environment for proper installation. Make sure the SUSE® Security containers can communicate with each other between hosts. Then review and edit the sample files for you environment.
Generally, it is important to do the following:
-
Label nodes appropriately. If you use node labels to control where the allinone or controller is deployed, label them before deploying.
-
Make sure volumes can be mapped properly. For example
volumes: - /var/neuvector:/var/neuvector - /var/run/docker.sock:/var/run/docker.sock - /proc:/host/proc:ro - /sys/fs/cgroup:/host/cgroup:ro -
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.
-
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.