Long-Term Supported Versions

    Innovation Versions

      Installing etcd

      Preparing the Environment

      Run the following command to enable the port used by etcd:

      firewall-cmd --zone=public --add-port=2379/tcp
      firewall-cmd --zone=public --add-port=2380/tcp
      

      Installing the etcd Binary Package

      Currently, the RPM package is used for installation.

      rpm -ivh etcd*.rpm
      

      Prepare the directories.

      mkdir -p /etc/etcd /var/lib/etcd
      cp ca.pem /etc/etcd/
      cp kubernetes-key.pem /etc/etcd/
      cp kubernetes.pem /etc/etcd/
      # Disabling SELinux
      setenforce 0
      # Disabling the Default Configuration of the /etc/etcd/etcd.conf File
      # Commenting Out the Line, for example, ETCD_LISTEN_CLIENT_URLS="http://localhost:2379".
      

      Compiling the etcd.service File

      The following uses the k8smaster0 machine as an example:

      $ cat /usr/lib/systemd/system/etcd.service
      [Unit]
      Description=Etcd Server
      After=network.target
      After=network-online.target
      Wants=network-online.target
      
      [Service]
      Type=notify
      WorkingDirectory=/var/lib/etcd/
      EnvironmentFile=-/etc/etcd/etcd.conf
      # set GOMAXPROCS to number of processors
      ExecStart=/bin/bash -c "ETCD_UNSUPPORTED_ARCH=arm64 /usr/bin/etcd --name=k8smaster0 --cert-file=/etc/etcd/kubernetes.pem --key-file=/etc/etcd/kubernetes-key.pem --peer-cert-file=/etc/etcd/kubernetes.pem --peer-key-file=/etc/etcd/kubernetes-key.pem --trusted-ca-file=/etc/etcd/ca.pem --peer-trusted-ca-file=/etc/etcd/ca.pem --peer-client-cert-auth --client-cert-auth --initial-advertise-peer-urls https://192.168.122.154:2380 --listen-peer-urls https://192.168.122.154:2380 --listen-client-urls https://192.168.122.154:2379,https://127.0.0.1:2379 --advertise-client-urls https://192.168.122.154:2379 --initial-cluster-token etcd-cluster-0 --initial-cluster k8smaster0=https://192.168.122.154:2380,k8smaster1=https://192.168.122.155:2380,k8smaster2=https://192.168.122.156:2380 --initial-cluster-state new --data-dir /var/lib/etcd"
      
      Restart=always
      RestartSec=10s
      LimitNOFILE=65536
      
      [Install]
      WantedBy=multi-user.target
      

      Note:

      • The boot setting ETCD_UNSUPPORTED_ARCH=arm64 needs to be added to ARM64;
      • In this document, etcd and Kubernetes control are deployed on the same machine. Therefore, the kubernetes.pem and kubernetes-key.pem certificates are used to start etcd and Kubernetes control.
      • A CA certificate is used in the entire deployment process. etcd can generate its own CA certificate and use its own CA certificate to sign other certificates. However, the certificate signed by the CA certificate needs to be used when the APIServer accesses the etcd client.
      • initial-cluster needs to be added to all configurations for deploying etcd.
      • To improve the storage efficiency of etcd, you can use the directory of the SSD as data-dir.

      Start the etcd service.

      $ systemctl enable etcd
      $ systemctl start etcd
      

      Then, deploy other hosts in sequence.

      Verifying Basic Functions

      $  ETCDCTL_API=3 etcdctl -w table endpoint status --endpoints=https://192.168.122.155:2379,https://192.168.122.156:2379,https://192.168.122.154:2379   --cacert=/etc/etcd/ca.pem   --cert=/etc/etcd/kubernetes.pem   --key=/etc/etcd/kubernetes-key.pem
      +------------------------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+
      |           ENDPOINT           |        ID        | VERSION | DB SIZE | IS LEADER | IS LEARNER | RAFT TERM | RAFT INDEX | RAFTAPPLIED INDEX | ERRORS |
      +------------------------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+
      | https://192.168.122.155:2379 | b50ec873e253ebaa |  3.4.14 |  262 kB |     false |      false |       819 |         21 |           21 |        |
      | https://192.168.122.156:2379 | e2b0d126774c6d02 |  3.4.14 |  262 kB |      true |      false |       819 |         21 |           21 |        |
      | https://192.168.122.154:2379 | f93b3808e944c379 |  3.4.14 |  328 kB |     false |      false |       819 |         21 |           21 |        |
      +------------------------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+
      

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.

      PR

      Just a small problem.

      I can fix it online!

      Bug Type
      Specifications and Common Mistakes

      ● Misspellings or punctuation mistakes;

      ● Incorrect links, empty cells, or wrong formats;

      ● Chinese characters in English context;

      ● Minor inconsistencies between the UI and descriptions;

      ● Low writing fluency that does not affect understanding;

      ● Incorrect version numbers, including software package names and version numbers on the UI.

      Usability

      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

      ● Unclear logic, such as missing classifications, items, and steps.

      Correctness

      ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

      ● Incorrect schematic or architecture diagrams;

      ● Incorrect commands or command parameters;

      ● Incorrect code;

      ● Commands inconsistent with the functions;

      ● Wrong screenshots.

      Risk Warnings

      ● Lack of risk warnings for operations that may damage the system or important data.

      Content Compliance

      ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

      ● Copyright infringement.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Submit
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份