In scenarios involving multiple groups and users on a Cerebras Wafer-Scale cluster within your organization, certain specific requirements may arise:
uid
) or group ID (gid
). This uid
or gid
, which identifies the job’s submitter on the Wafer-Scale cluster, configures the SecurityContext within a Kubernetes pod responsible for managing the appliance and granting access to NFS-mounted storage.
The root
user on the user nodes maintains a file containing a secret key. This key is also stored within the User-Auth Library
in the Wafer-Scale cluster. Access to this secret file is limited to the root
user, preventing other users from reading or writing to it. A binary file, owned by the root
user and inaccessible to non-privileged users, is invoked. When called by non-privileged users, this binary file invokes the system calls to retrieve uid
, gid
, or groups
information for the invoking user, uses the secret key to encrypt the user’s information, and generates an authentication token with a predefined time-to-live. Subsequently, this authentication token is embedded in the job request to be submitted to the cluster management server.
The cluster management server performs validation of the authentication token, extracting relevant user and group details and then launches the job only if the token is verified as valid.