Host requirements (Kubernetes)

Type	Host Requirement	Explanation
User	A user (example: hyperscale_os) with the following permissions is required: Permission to run helm commands Permission to run `kubectl` commands	These permissions are required to be able to install helm charts and manage the Kubernetes resources.
NFS Client Services	NFS client services must be enabled on the host.	NFS client service is required to be able to mount an NFS shared storage from where the Hyperscale Compliance Orchestrator will be able to read the source files and write the target files. For more information, see NFS Server Installation.
Staging area directory permissions	The ‘staging_area’ directory, along with the directory(`hyperscale`) one level above, require the following permissions, based on the UID/GID of the OS user so that the Hyperscale Compliance Orchestrator and the Continuous Compliance Engine(s) can perform read/write/execute operations on the staging area: If the Hyperscale Compliance OS user has a UID of 65436, then the ‘staging_area’ directory, along with the directory(`hyperscale`) one level above, must have a UID of 65436 and 700 permission mode. If the Hyperscale Compliance OS user has a GID of 50 and does not have a UID of 65436, then the ‘staging_area’ directory, along with the directory(`hyperscale`) one level above, must have a GID of 50 and 770 permission mode.	These permissions on the staging area directory are required for the Hyperscale Compliance containers and the continuous compliance engines to be able to read/write into the staging area.
Installation Directory	A directory to download and manage helm charts.
Hardware Requirements	Minimum: 8 vCPU, 64 GB of memory, 50GB OS disk. Recommended: 16 vCPU, 128GB of memory, 50GB OS disk.