Get a Linux Server (RHEL 9 / Ubuntu) CPU 4 cores RAM 16 GB
Download IRIS from HCL Volt MX GO Early Access Release
Get authentication token from HCL Container Repository
Install and configure K3s
Complete preparatory procedure for first time installation of Volt MX Go
Install Domino/Keep
Install MySql for Foundry
Install Foundry
Create a Foundry administrator account
Connect to Domino Server from Notes Client
Install Volt MX Go Iris and use it to develop applications.
Here I am having doubts about:
Point 1, can I use a low RAM server let's say 8 GB, will it support Volt MX GO?
Point 2, HCL Volt MX GO Early Access Release does not include any installation media for VOLT MX Go server?
Kubernetes Light, Domino/Keep, MySQL, Foundry iare not needed to be downloaded separately from HCL Flexnet?
Should I right away start with the K3S installation, after getting a Linux Sever Machine, without any server hardening and installing any dependencies?
Let me see if I can answer your questions. I'm focused on the containerized solution and a generalist out side of that, so I'll do my best and look for others to chime in where needed.
Your steps 1-10 look correct.
1) I doubt 8 GB RAM will suffice. Perhaps with 12 GB. We've got 4 processes running Tomcat and a Foundry component (Console, API Portal, Identity, Integration), MySQL, and a Domino Server. All of this on top of a Kubernetes cluster. That's quite a bit of tech that we're trying to run on a single machine.
2) Volt MX GO is an offering comprised of Volt MX (Foundry, Iris and its associated componentry), a new Foundry Domino adapter, and a Domino Server/Domino REST API. All together these make up the Volt MX Go offering. There is no single Volt MX GO server.
3) Foundry server components & the Domino REST API container (includes Domino server) are pulled from HCL's container repository at https://hclcr.io. Iris is downloaded from HCL Flexnet. K3s, Rancher Desktop , and MySQL docker image must be downloaded from "standard" open source sites that we have documented.
4) Certainly if your deployment is going to be internet facing you would want to harden the server. And best practices usually involve some degree of hardening even if only exposed on your corporate intranet. Assuming a corporate intranet, you might have the best luck to first install K3s and following their hardening guide which can be found at https://ranchermanager.docs.rancher.com/pages-for-subheaders/k3s-hardening-guide. I'm thinking the less hardening you do initially and get everything installed and running (and verified base functionality) then come back and harden and verify its still all working and accessible may be the easiest path.