Help Center/ ServiceStage/ User Guide/ Environment Management/ Managing CCE Resources/ Managing Plug-ins/ Managing Sermant Injector/ Installing Sermant Injector
Updated on 2024-12-16 GMT+08:00
View PDF
Share

Installing Sermant Injector

Sermant Agent is automatically mounted to container-deployed Spring Cloud applications through the Sermant Injector plug-in. These applications are connected to the ServiceComb engine or registry/configuration center with security authentication disabled through Sermant Agent. For details about Sermant Agent, see Sermant-agent User Manual.

Compared with Spring Cloud Huawei, Sermant Agent allows you to access the engine and use functions such as application registry and discovery, full-link dark launch, graceful startup and shutdown, and label routing without modifying application code. However, microservice governance is not supported.

Use either Sermant Agent or Spring Cloud Huawei to connect Spring Cloud applications to the exclusive ServiceComb engine. Do not use them at the same time to avoid conflicts.

This section describes how to install Sermant Injector for a CCE cluster bound to a Kubernetes environment.

Prerequisites

  1. A Kubernetes environment has been created. For details, see Creating a Kubernetes Environment in Resource Management Mode.
  2. A CCE cluster later than 1.15 has been bound in the environment. For details, see Binding a CCE Cluster.
  3. Namespace cse of the bound CCE cluster cannot contain the configuration item sermant-injector, key sermant-injector-secret, workload sermant-injector, or service sermant-injector. Otherwise, the plug-in installation will fail.
  4. An exclusive ServiceComb engine 2.4.0 or later or registry/configuration center with security authentication disabled has been managed in the environment. For details, see Managing Basic Resources.

Installing Sermant Injector

  1. Log in to ServiceStage.
  2. Choose Environment Management. The Environment Management page is displayed.
  3. Click the target environment. The Overview page is displayed.
  4. Choose Plug-in Management.
  5. Select Sermant Injector under Addons.

    • For a non-HA environment, click install and then go to 6.
    • For an HA environment, select the AZ where the CCE cluster on which the Sermant Injector plug-in is to be installed is located, and go to 6.

  6. Set the parameters by referring to the following table.

    Parameter

    Description

    CCE Cluster

    By default, a managed CCE cluster in the current environment is selected.

    Server Type

    CPU architecture of the CCE cluster.

    • x86_64
    • aarch64

    Associated Microservice Engine

    Select the exclusive ServiceComb engine or registry/configuration center for installing the plug-in.

  7. Click OK.

    • After the Sermant Injector plug-in is successfully installed, the content listed in the following table is created.

      Name

      Description

      Namespace

      Create a namespace named cse in the CCE cluster selected in 6.

      NOTE:

      If the CCE cluster selected in 6 already has a namespace named cse, the namespace will be reused when the Sermant Injector plug-in is installed.

      ConfigMaps

      In namespace cse of the CCE cluster selected in 6, create a configuration item named sermant-injector.

      Secrets

      In namespace cse of the CCE cluster selected in 6, create a secret named sermant-injector-secret.

      Workloads

      In namespace cse of the CCE cluster selected in 6, create a workload named sermant-injector.

      Services

      In namespace cse of the CCE cluster selected in 6, create a service named sermant-injector.
    • If the Sermant Injector plug-in fails to be installed, try again by referring to Reinstalling Sermant Injector.
    • If a CCE cluster with the Sermant Injector plug-in installed is bound to another environment, manage the exclusive ServiceComb engine or registry/configuration center associated with the Sermant Injector plug-in in that environment. Otherwise, the Sermant Injector plug-in will be unavailable in that environment.

      For details about how to manage exclusive ServiceComb engines, see Managing Basic Resources.