System Requirements
Compatible Kubernetes Versions
This version of the Saagie installer is compatible with Kubernetes versions 1.20.x
, 1.21.x
, 1.23.x
, and 1.24.x
.
Compatible Cgroup Version
This version of Saagie must be compatible with the cgroup v1
version of the Linux cgroup
API.
To check which cgroup version your distribution uses, run the following command on your node:
stat -fc %T /sys/fs/cgroup/
The output for cgroup v1
must be tmpfs
.
For more information, see the Kubernetes documentation.
Domain Name System (DNS) Entry
Your DNS entry will be used only at the end, but you should determine it before starting the installation process using the following pattern: prefix-suffix[.subdomain].domain.com
.
The entire entry must respect DNS norms according to RFC-1034. |
Component | Details | Example | ||
---|---|---|---|---|
|
Must be up to a maximum of 12 characters, with only letters and numbers. Hyphens and special characters are not supported.
|
|
||
|
For Saagie to work properly, your DNS entry must contain a suffix. |
|
||
|
This is the company domain to which your Saagie platform will be connected. |
|
||
|
You can add as many subdomains as required after the component |
|
Examples
-
URL without subdomain:
dunder-workspace.dundermifflin.com
-
URL with subdomain:
dunder-workspace.paper.dundermifflin.com
Pod Security Policies (PSP) Requirements
Saagie deployment requires two Pod Security Policies (PSP). The admission controller can be enabled or disabled:
Status | Details |
---|---|
|
No effect on your cluster. |
|
Saagie will run as expected. |
|
Will not prevent Saagie from running as expected. |
PSPs are applied to a Service Account through a ClusterRole
and the related ClusterRoleBinding
.
PSPs and the related ClusterRole
and ClusterRoleBinding
are provided in the requirements.yml
file that will be created later in the installation process.
Supported Browsers
Use the following web browsers to get the most out of Saagie:
-
Google Chrome (latest stable version)
-
Mozilla Firefox (latest stable version)
-
Microsoft Edge (latest stable version)
The minimum supported screen resolution is 1366x768 pixels. Browser and system settings, such as scaling, zooming, and window size, will affect browser compatibility.
Minimum Machine Requirements
Regardless of your cloud provider, you must meet the following minimum machine requirements:
-
3 nodes
-
4 vCPU per node
-
16 GB RAM per node
-
300 GB of distributed disk storage
Node Isolation
You must meet this requirement if you choose to isolate the workload of your platforms on dedicated nodes. This question is asked when configuring Saagie.
|
Node isolation allows you to isolate the execution of the Saagie installation, as well as the execution of each platform. This is done by specializing the cluster nodes with appropriate node labeling. A proper node labeling will allow jobs and apps to run on nodes dedicated to a platform and prevent them to intrude on another platform’s resources.
The accuracy of the Monitoring and
Operations module pages in Saagie depends on the isolation mode of your platforms.
If your workload isolation has not been configured, the |
For the best experience, add the correct label to each node to dedicate them to a platform. This must be done before starting configuring your Saagie platforms, when configuring your cluster. More specifically, in the Creating or Configuring Your Cluster part of the page corresponding to your provider.
In isolated mode, you must have at least one common node with the following labels: io.saagie/installationId: <installationId> io.saagie/type: common These labels will allow you to dedicate the common nodes to the Saagie installation and isolate it from the rest of your workload. If you do not have a common node labeled as such, Saagie will not start. The other nodes must be labeled as follows: io.saagie/installationId: <installationId> io.saagie/type: platform io.saagie/platform-assignable: <platformId> Where:
If a node is not labeled, it will not be used in the Saagie context and will not be displayed in the |