User Information

Periodically change the user password to prevent risks caused by long-term use of the same password.

System Users

User	Description	Initial Password	Password Changing Method
root	-	User-defined	Run the passwd command to change the password.
HwHiAiUser	Running user of the RUN driver package	User-defined	Run the passwd command to change the password.
hwMindX	Default running user of cluster scheduling components. The default value is nologin.	None	-
HwBaseUser	User for running driver-related devices on Atlas 200I SoC A1 core boards. It is created by the driver RUN package or user during driver installation. The default value is nologin.	None	-
HwDmUser	User for running driver-related devices on Atlas 200I SoC A1 core boards. It is created by the driver RUN package or user during driver installation. The default value is nologin.	None	-

Container Users in Cluster Scheduling Components

User	Description	Initial Password	Password Changing Method
root	-	None	-
HwHiAiUser	Running user of the driver .run package. nologin is used in containers of cluster scheduling components not installed on Atlas 200I SoC A1 core boards, indicating that the user cannot be used for login.	None	-
hwMindX	Default running user of containers of cluster scheduling components. The default value is nologin.	None	-
HwBaseUser	User for running driver-related devices on Atlas 200I SoC A1 core boards. It is recommended that a user be created in containers of cluster scheduling components.	None	-
HwDmUser	User for running driver-related devices on Atlas 200I SoC A1 core boards. It is recommended that a user be created in containers of cluster scheduling components.	None	-

Users in the Nginx Container (Not Involved in Non-Security Hardening Scenarios)

User	Description	Initial Password	Password Changing Method
nginx	Account for running the Nginx container	None	-

Users of the alpha Base Image in the Dockerfile Example

User	Initial Password	Password Changing Method
root	None	-
bin	None	-
daemon	None	-
adm	None	-
lp	None	-
sync	None	-
shutdown	None	-
halt	None	-
mail	None	-
news	None	-
uucp	None	-
operator	None	-
man	None	-
postmaster	None	-
cron	None	-
ftp	None	-
sshd	None	-
at	None	-
squid	None	-
xfs	None	-
games	None	-
cyrus	None	-
vpopmail	None	-
ntp	None	-
smmsp	None	-
guest	None	-
nobody	None	-

Users of the Ubuntu Base Image in the Dockerfile Example

User	Initial Password	Password Changing Method
root	None	-
daemon	None	-
bin	None	-
sys	None	-
sync	None	-
games	None	-
man	None	-
lp	None	-
mail	None	-
news	None	-
uucp	None	-
proxy	None	-
www-data	None	-
backup	None	-
list	None	-
irc	None	-
gnats	None	-
nobody	None	-
_apt	None	-

Kubernetes Service Accounts

**Table 1** List of service accounts created by each component in Kubernetes
Account Name	Description
volcano-controllers	User created in Kubernetes for the controller component of the open source Volcano.
volcano-scheduler	User created in Kubernetes for the scheduler component of the open source Volcano.
ascend-device-plugin-sa-910	If you use YAML to start the service, the account is created in Kubernetes. The account name varies depending on the device model.
ascend-device-plugin-sa-310p
ascend-device-plugin-sa-310
ascend-operator-manager	If you use YAML to start the service, the account is created in Kubernetes, for example, ascend-operator-v{version}.yaml.
resilience-controller	If you use YAML without tokens to start the service, the account is created in Kubernetes, and proper permissions is granted to the account. Security hardening is recommended.
noded	If you use YAML to start the service, the account is created in Kubernetes, for example, noded-v{version}.yaml.
clusterd	If you use YAML to start the service, the account is created in Kubernetes, for example, clusterd-v{version}.yaml.
default	Automatically created in Kubernetes when MindCluster components or open-source Volcano is deployed.

Parent topic: Appendixes