Differences Between Container and Binary Deployment

Table 1 Differences between the two component installation methods

Component

Installation Method

Difference

NPU-Exporter

Binary

  • Deployed on physical machines as system services.
  • After the capability is configured, the common user (hwMindX) can run the capability.

Container

  • Uses Kubernetes as the scheduling management platform and requires the privileged container and root user.

Ascend Device Plugin

Binary

  • Deployed on physical machines as system services.
  • After the capability is configured, the common user (hwMindX) can run the capability.
  • When Volcano is used, you do not have the permission to access Kubernetes. You need to import the KubeConfig file.

Container

  • Uses Kubernetes as the scheduling management platform and requires the privileged container and root user.
  • When Volcano is used, both the ServiceAccount and the KubeConfig file can be used.