Installing MinIO Enterprise SNMD

• Create a self-signed certificate for the app. The Certificates setting is not required for a basic configuration but is required when setting up multi-mode configurations and when using MinIO as an immutable target for Veeam Backup and Replication.

• Set a pool for applications to use if not already assigned.

• (Optional) Create a new TrueNAS user to serve as the administrator for the app. You can use the default user or add a new user. When you create a new user select Create New Primary Group, and select the appropriate group in the Auxiliary Group for the type of user you want to create. Make note of the UID for the new user to add in the installation wizard.

• Create the required dataset(s).

You can have multiple deployments of the same app (for example, two or more from the stable or enterprise trains, or a combination of the stable and enterprise trains).

To install the Minio Enterprise app, go to Apps, click on Discover Apps and then either scroll down to locate the enterprise train version of the Minio widget, or search for it by typing MinIO in the search field to show the app widget.

Click on the MinIO Official Enterprise widget to open the MinIO information screen.

Click Install to open the Install MinIO configuration screen.

Accept the defaults in Application Name or enter a name for your MinIO application deployment.

Accept the default in Version, which populates with the current MinIO version. TrueNAS displays update information on the Installed application screen when an update becomes available.

Enter credentials to use as the MinIO administration user. If you have existing MinIO credentials, enter these or create new login credentials for the first time you log into MinIO. Enter a name for the MinIO administrator user in MinIO Root User, which is the equivalent of the MinIO access key. A username for the root user (MinIO access key), entered in MinIO Root User, is limited to five to 20 characters long. For example admin or admin1.

Enter the administration user password in MinIO Root Password, which is the login password for that user or the MinIO secret key. The root user password (MinIO secret key), entered in MinIO Root Password, is limited to eight to 40 random characters. For example, MySecr3tPa$$w0d4Min10.

Select Anonymous to hide sensitive information from logging, or Quiet to disable startup information.

To configure a multi-mode deployment, select Enabled. MinIO recommends using MNMD for enterprise-grade performance and scalability.

Scroll down to or click on Storage Configuration on the list of wizard sections.

To create the storage volume, set Type to Host Path (Path that already exists on the system) which is the recommended option for MinIO. Mount Path populates with the default /data1. Enter the path or browse to and click on the data1 dataset location to populate Host Path.

Click Add to the right of Data Directories to show the storage fields to add the other datasets representing drives in for multi-mode configurations. Click Add for each additional dataset (data2, data3, and data4). If you change the configuration of a basic installation or SNMD, you can use the data1 dataset in the configuration and add the three additional datasets.

Change the Mount Path to match each dataset path in Host Path. For example, for data2 enter /data2 in the Mount Point field.

Repeat these storage instructions to add all four storage volumes and mount points. When finsihed you should have four storage volumes and mount points configured.

Accept the default values in Resources Configuration or to customize the CPU and memory allocated to the container (pod) the Minio app uses, enter new values in the CPU and Memory (in MB) fields. Tune these limits as needed to prevent the application from overconsuming system resources and introducing performance issues.

By default, this application is limited to use no more than 2 CPU cores and 4096 megabytes available memory. The application might use considerably less system resources.

Click Install to complete the installation.

The Installed applications screen opens showing the MinIO application in the Deploying state, then changes to Running when the application is ready to use.

Click Web Portal to open the MinIO sign-in screen.

Accept the default value or enter a name in Application Name field. In most cases use the default name, but if adding a second deployment of the application you must change this name.

Accept the default version number in Version. When a new version becomes available, the application shows an update badge and the Application Info widget on the Installed applications screen shows the Update button.

MinIO credentials establish the login credentials for the MinIO web portal and the MinIO administration user.

Enter existing MinIO credentials if you already have a MinIO account, or create new login credentials for the first time you log into MinIO. The Root User is the equivalent of the MinIO access key. The Root Password is the login password for that user or the MinIO secret key.

A username for the root user (MinIO access key), entered in Root User, is limited to five to 20 characters long. For example admin or admin1.

The root user password (MinIO secret key), entered in Root Password, is limited to eight to 40 random characters. For example, MySecr3tPa$$w0d4Min10.

To configure a multi-mode deployment, select Enabled. MinIO recommends using MNMD for enterprise-grade performance and scalability. See the related MinIO articles listed below for SNMD and MNMD configuration tutorials.

Select Quiet to disable startup information and not show it in the logs.

Select Anonymous to hide sensitive information and not show it in the logs.

(Optional) Click Add to the right of Additional Environment Variables to show the fields to enter the variable. The installation wizard configures all required environment variables, so only use this option to further customize your MinIO deployment. Refer to MinIO documentation for more information on environment variables they allow and use.

Some TrueNAS apps have predefined run-as user and group IDs. These assignments vary based on the app train and other variables such as installing but not running as the root user.

Default user and group IDs are:

• 473 for the MinIO stable train app.
• 568 (apps user), used in some community apps and all apps in the enterprise train
• 999 (netdata user), used for all postgres storage volumes
• 0 (root user).

Accept the default user and group ID in the User and Group Configuration section or enter the user ID for a new TrueNAS user created to serve as the administrator for this app.

Create any app administrator user before installing the application, and take note of the UID. Enter this user ID when configuring the user for the app and as the user when setting up storage volume permissions.

Accept the default port numbers in API Port and Console Port (Web UI), which are the port numbers MinIO uses to communicate with the app and web portal.

Enter the system IP address in URL format followed by the port number for the API separated by a colon in Server URL. For example, https://10.123.12.123:30000.

Enter the system IP address in URL format followed by the port number for the web portal separated by a colon in Console URL. For example, https://10.123.12.123:30001.

MNMD MinIO installations require HTTPS for both Server URL and Console URL to verify the integrity of each node. Standard or SNMD MinIO installations do not require HTTPS.

Do not select Host Network.

MinIO does not require a certificate for a basic configuration and installation of MinIO Enterprise, but if installing and configuring multi-mode SNMD or MNMD, you must create a self-signed certificate.

A SNMD configuration can use the same self-signed certificate created for MNMD, but a MNMD configuration cannot use the certificate created for a SNMD configuration because that certificate only includes the IP address for one system. Create this same self-signed certificate for the MNMD cluster on each system (node) in the cluster!

MinIO storage settings include the option to add storage volumes to use inside the container (pod). To allow TrueNAS to create a storage volume, leave Type set to the default ixVolume *(Dataset created automatically by the system). This adds a storage volume for the application that can be found nested under the hidden ix-apps dataset. To see this, create a recursive snapshot of the ix-apps dataset.

To use the data existing dataset, select Host Path (Path that already exists on the system) from the Type dropdown list. The Mount Path field populates with /data1 as the first storage volume for a basic installation. Enter the path or browse to select the data1 dataset and populate the Host Path field.

Click Add to the right of Data Directories to add the datasets created and representing drives in for multi-mode configurations. Click Add for each dataset (data1, data2, data3, and data4).

If configuring either MNMD or SNMD, you must all all four datasets to each system in the cluster. These datasets represent the disk in the multi-disk configurations.

Change the Mount Path to correspond to the dataset path entered or selected in Host Path. Additional mount points are /data2, /data3, or /data4.

You can select Enable ACL to modify dataset permissions and add ACL entries.

Select Enable ACL to show the ACL and ACE Entries options.

Configuring ACE Entries

Enter or browse to select the dataset and populate Host Path.

Next, click Add to the right of ACL Entries to show the permissions settings. Set ID Type to Entry is for a USER or Entry is for a GROUP. If you configured a group in TrueNAS that you want to give access to instead of a single user, set the ID to the group option and enter the GID for that group.

Enter the UID as one of the following:

• The default app user:
  • 568 for apps in all trains if the app can run as any non-root user.
  • 999 for all postgres storage volumes.
  • 0 if running as root.
  • 473 for MinIO app in the stable train.
• The run-as-user UID set as a default for the app. The run-as user shows on the app details screen in the Run As Content widget, and on the Installed application screen after the app deploys. You can refer to the tutorial for the app, or look in the questions.yaml file found in the GitHub repository for the application to find this UID/GID.
• The user ID for the new or existing TrueNAS user added to serve as the administrator for the app.

If the app shows User and Group Configuration settings, the default UID shows on the screen. If not, choose the run-as user ID found in the Run As Content widget.

Use the default user ID 999 for all postgres storage volumes, not the run-as user.

If you created a new TrueNAS user to serve as the app administration user, add an entry record and enter the UID for this user in addition to the run-as user ID.

When adding the ACL entry for the run-as user, default user, and/or optional TrueNAS app administrator user, and postgres user ID, set the Access permissions level to FULL CONTROL.

Select Force Flag to apply the ACL even if the path has existing data. This allows you to update the app when an update is available.