SystemLink Enterprise implements a server-client architecture to transmit data over a connected network between your systems and server. Use the minimum required SystemLink Enterprise system components as a starting point for building your system.

For more information on component software that is compatible with your version of SystemLink Enterprise, refer to Related information.

Table 3. Minimum Required SystemLink Enterprise System Components
Component Description and Recommendations
Kubernetes cluster
  • A Kubernetes cluster running Kubernetes with Linux worker nodes.
  • Helm to configure and to install the application.
  • Dynamic Volume Provisioning enabled on the cluster.
    Note When deploying to an Amazon Web Services cluster, use Amazon Elastic Block Store (EBS) volumes. SystemLink Enterprise does not support Amazon Elastic File Storage (EFS) volumes.
  • An NFS storage provisioner, or equivalent storage class, with ReadWriteMany access.
  • Properly configure the inotify parameters in the Kubernetes nodes, such as max_user_instances, max_user_watches, and max_queued_events.
    Note For more information, refer to the configuration guide for your Linux distribution.
External data storage
  • An Amazon S3 or Amazon S3-like file storage interface.
  • A PostgreSQL instance or replica set.
  • A MongoDB instance or replica set.
  • An Elasticsearch instance.
Networking and user authentication
  • An NGINX Ingress Controller for HTTP communication.
  • DNS and three distinct host names.
  • An identity provider with support for the OpenID Connect protocol.
  • Network access to the NI Artifact repository.
SystemLink Client Use SystemLink Client to communicate with targets. For more information on target requirements, refer to Related information.

Sizing a SystemLink Enterprise Cluster

SystemLink Enterprise runs a minimum of two Kubernetes worker nodes and can scale to as many nodes as needed for your organization. To determine specific hardware requirements for your deployment, contact your account representative.

For a production deployment, NI encourages administrators to provision enough worker nodes to enable a high availability configuration.