Before installing Wallaroo, verify that the following hardware and software requirements are met.

Cluster Requirements

The following requirements are specific to the cluster that hosts Wallaroo.

Environment Hardware Requirements

The following system requirements are required for the minimum settings for running Wallaroo in a Kubernetes cloud cluster.

• Minimum number of nodes: 4
• Minimum Number of CPU Cores: 8
• Minimum RAM per node: 16 GB
• Minimum Storage: A total of 625 GB of storage will be allocated for the entire cluster based on 5 users with up to four pipelines with five steps per pipeline, with 50 GB allocated per node, including 50 GB specifically for the Jupyter Hub service. Enterprise users who deploy additional pipelines will require an additional 50 GB of storage per lab node deployed.

Wallaroo recommends at least 16 cores total to enable all services. At less than 16 cores, services will have to be disabled to allow basic functionality as detailed in this table.

Note that even when disabling these services, Wallaroo performance may be impacted by the models, pipelines, and data used. The greater the size of the models and steps in a pipeline, the more resources will be required for Wallaroo to operate efficiently. Pipeline resources are set by the pipeline configuration to control how many resources are allocated from the cluster to maintain peak effectiveness for other Wallaroo services. See the following guides for more details.

• Wallaroo SDK Essentials Guide: Pipeline Deployment Configuration
• Wallaroo MLOps API Essentials Guide: Pipeline Management

To install Wallaroo with minimum services, a configuration file will be used as parts of the kots based installation. For full details on the Wallaroo installation process, see the Wallaroo Install Guides.

Enterprise Network Requirements

The following network requirements are required for the minimum settings for running Wallaroo:

• For Wallaroo Enterprise users: 200 IP addresses are required to be allocated per cloud environment.

  • Wallaroo only supports RFC-1918 private addresses, that is 10/8, 172.16/12 , or 192.168/16 networks.
    • RFC-6598 are not supported. These include 100.64/10.

• For Wallaroo Community Edition users: 98 IP addresses are required to be allocated per cloud environment.

• DNS services integration is required for Wallaroo Enterprise edition. See the DNS Integration Guide for the instructions on configuring Wallaroo Enterprise with your DNS services.

  DNS services integration is required to provide access to the various supporting services that are part of the Wallaroo instance. These include:

  • Simplified user authentication and management.
  • Centralized services for accessing the Wallaroo Dashboard, Wallaroo SDK and Authentication.
  • Collaboration features allowing teams to work together.
  • Managed security, auditing and traceability.

As part of the installation, Wallaroo deploys an envoy proxy. This terminates into the Wallaroo TLS and reverse proxies HTTPS to the Wallaroo services. If the installation ingress_mode is set to internal or external, the envoy proxy is type LoadBalancer with the cloud-appropriate annotations.

Wallaroo does not create Ingress or API Gateway objects as part of the installation.

Certificate Requirements

Wallaroo requires TLS certificates that match the host name used to access Wallaroo services. The following details the how to generate CA-signed certificates used for the installation procedures.

1. Create a CA-signed TLS certificate for your Wallaroo domain with the following settings:
   1. Certificate Authority Options:
      1. Use a public Certificate Authority such as Let’s Encrypt or Verisign. In general, you would send a Certificate Signing Request to your CA and they would respond with your certificates.
      2. Use a private Certificate Authority (CA) to provide the certificates. Your organization will have procedures for clients to verify the certificates from the private CA.
      3. Use a Wallaroo certificate and public name server. Contact our CSS team for details.
   2. Wallaroo Domain:
      1. Set the certificate’s Subject CN to your Wallaroo domain. For example, if the Wallaroo Domain wallaroo.example.com, then the Subject CNs would be: wallaroo.example.com.
   3. Save your certificates.
      1. You should have two files: the TLS Certificate (.crt) and TLS private key (.key). Store these in a secure location - these will be installed into Wallaroo at a later step.

wallaroo-fluent-bit
wallaroo-multi-scaler
wallaroo-prometheus
wallaroo-rest-api
wallaroo-wallsvc