Help Center/ ServiceStage/ Best Practices/ Hosting a Spring Boot Application on ServiceStage/ Upgrading Component Versions Using ELB Dark Launch
Updated on 2024-09-27 GMT+08:00
View PDF
Share

Upgrading Component Versions Using ELB Dark Launch

  1. Go to the ServiceStage console.
  2. Choose Application Management. The application list is displayed.
  3. Click the application created in Creating an Application (for example, springGuides). The Overview page is displayed.
  4. On the Component List tab, click the component created in Deploying and Accessing Spring Boot Applications (for example, spring-boot). The Overview page is displayed.
  5. In the upper right corner of the page, click Upgrade.
  6. Set Upgrade Type to Dark Launch and click Next.
  7. Set mandatory parameters for dark launch by referring to the following table. Retain the default values for other parameters.

    Parameter

    Description

    Source Code/Image

    The value is fixed to the GitHub source code repository selected during component creation and deployment.

    1. Click Modify.
    2. Authorization: Select the authorization information created in Setting GitHub Repository Authorization.
    3. Username/Organization: Select the username used to log in to GitHub in Forking Source Code.
    4. Repository: Select the name of the Spring Boot source code repository that has been forked to your GitHub account. For example, gs-spring-boot-kubernetes.
    5. Branch: Select main.

    Command
    1. Select Custom command.
    2. Enter the following command in the command text box: 
      cd ./complete/;mvn clean package

    Component Version

    Enter 1.0.1.

    Deployment Architecture
    1. Click Select.
    2. Select Type 3: Connects the service to load balancer (microservice A implements dark launch).
    3. Click OK.

    Dark Launch Policy

    Select Traffic ratio-based.

    Traffic Ratio
    • Traffic Ratio: percentage of traffic directed to the new version. Set it to 50.
    • Current Traffic Ratio: percentage of traffic directed to the current version. It is automatically set to 50.

    Instances Deployed for Dark Launch

    Select Canary (increase, then decrease instances).

    First Batch of Dark Launch Instances

    Set this parameter to 1.

    Deployment Batch with Remaining Instances

    Set this parameter to 1.

  8. Click Upgrade.

    Wait until the component status changes from Upgrading/Rolling back the component to Releasing, indicating that the component is released in dark launch.

  9. Perform Accessing Spring Boot Applications multiple times. If "Greetings from Spring Boot!" and "Hello" are displayed alternately on the page, the dark launch version of ELB is released.