●
It is recommended not to make any changes to the default set of Kubernetes and Kerberos configurations
without consulting Cray Support, as doing so can adversely affect the functionality of the system in the secure
service mode.
●
Enabling of the
PermitUserEnvironment
option in
sshd_config(5)
or the passing of environment
variables beyond those listed on the
ssh(1)
manual page.
●
Changing any settings listed in
/etc/environment
into login sessions on Urika-GX physical nodes outside
of the system through the login mechanism.
●
Modifying the list of whitelist commands. For a list of commands that are part of the whitelist, see
page 183
●
Tenant NameNode configuration is managed automatically by the Urika-GX tenant management scripts.
Manually altering the configurations of the tenant NameNode is not supported.
●
Tenant names may only contain:
○
the letters a-z
○
the numbers 0-9
○
the characters '
-
' and '
.
'
NOTE: The name '
default
' is reserved for the sample tenant configuration and cannot be used as a
tenant name.
●
The following items need to be kept under consideration while using the
ux-tenant-alter-vm
command:
○
Number of CPUs: At least 2 CPUs need to remain available when the number of CPUs is changed by this
script. That is, if there are
N
number of CPUs, a maximum of
N
-2
CPUs can be assigned to a VM.
○
Amount of memory: At least 50% of the memory must remain available after a VM has been assigned
memory using this command.
The Urika-GX System
S3016
14
