Starting the NodeD

Procedure

  1. Log in to each worker node as the root user and run the following command to check whether the image and version are correct:
    docker images | grep noded

    Example:

    root@ubuntu:~# docker images|grep noded 
    noded                               v3.0.0              ef801847acd2        29 minutes ago      133MB
    • If yes, go to 2.
    • If no, create an image and distribute it. For details, see Creating an Image.
  2. Copy the YAML file in the directory where the NodeD software package is decompressed (for example, /home/noded) to any directory on the Kubernetes master node (for example, /home/noded). If the NodeD software package is decompressed on the Kubernetes master node, you do not need to copy the YAML file.
    cd /home/noded
    scp noded-*.yaml root@{IP_address_of_the_Kubernetes_master_node}:/home/noded
  3. Skip this step if you do not need to modify the component startup parameters. Otherwise, modify the NodeD startup parameters in the YAML file based on your requirements. For details about the startup parameters, see Table 1. You can run the ./noded -h command to view the parameter descriptions.
  4. Start the NodeD.
    • Run the following command if the KubeConfig certificate is imported:
      kubectl apply -f noded-without-token-{version}.yaml
    • Run the following command if the KubeConfig certificate is not imported:
      kubectl apply -f noded-*.yaml

    The following is an example:

    root@ubuntu:/home/noded# kubectl apply -f noded-without-token-v3.0.0.yaml
    daemonset.apps/noded created
    root@ubuntu:/home/noded# kubectl get pod -n mindx-dl
    NAME                              READY   STATUS    RESTARTS   AGE
    ...
    noded-fd6t8                       1/1     Running   0          74s
    ...

Parameters

Table 1 NodeD startup parameters

Parameter

Type

Default Value

Description

-heartbeatInterval

int

5

Interval for sending heartbeat messages. The value range is (0, 300], in seconds. The interval is written into Annotation (the noded/heartbeat-interval field) of the node during NodeD startup.

-version

bool

false

NodeD version.

-logLevel

int

0

Log level.

  • -1: debug
  • 0: info
  • 1: warning
  • 2: error
  • 3: critical

-maxAge

int

7

Log backup time limit. The value ranges from 7 to 700, in days.

-logFile

string

/var/log/mindx-dl/noded/noded.log

Log file.

NOTE:

If the size of a log file exceeds 20 MB, automatic dump is triggered. The maximum size of a log file cannot be changed.

-maxBackups

int

30

Maximum number of dumped log files that can be retained. The value range is (0, 30].

-kubeConfig

string

/etc/mindx-dl/noded/.config/config6

Path for storing the encrypted KubeConfig file by default. The KubeConfig file in a user-defined path is also supported. If the configuration file does not exist in the default path, InClusterConfig is enabled.

NOTE:

This file must be encrypted using the certificate import tool. A plaintext file is not supported.

-h

None

N/A

Help information.