Skip to main content

Kubernetes Version Middleware Installation Guide

This guide is designed to help customers quickly experience the K8s version in situations where they cannot provide their own Mysql, S3, CICD, etc.

tip

MySQL databases started using Kubernetes do not have high availability and are not recommended for use in production environments to store data. The platform recommends connecting to users' own external databases.

1. Prerequisites​

To deploy the middleware required by WeDa, the following conditions must be met:

  • CPU: 2 cores, Memory: 4GB, Disk: 100GB
  • By default, docker must be installed with a version greater than 20.0.0
  • Ansible must be installed. It can be installed by executing yum install ansible or `apt-get install ansible

2. Start Deployment​

  • 2.1. Log in to the deployment environment and switch to the root user

  • 2.2. Execute ssh-keygen to configure password-less login

  • 2.3 cd /root/.ssh, copy the content from the file ending with .pub to authorized_keys and save

  • 2.4 Download and extract the installation package: `wget -L -O weda-middleware.zip https://software-1302110647.cos.ap-guangzhou.myqcloud.com/rc/lastest/weda-middleware.zip && unzip weda-middleware.zip && cd weda-middleware

  • 2.5 Execute ansible-playbook -i hosts site.yaml to complete the installation

  • 2.6. By default, only the giteness service is installed; MySQL and S3 are not provided. They will be automatically installed when enabled (free maintenance is not included)

  • 2.7. To enable automatic installation of MySQL or S3 (skip if not needed), navigate to weda-middleware/group_vars and edit the middleware file

## Installation required, set to True
mysql_enabled: True

## Installation required, set to True
s3_enabled: True

3. Middleware Information​

tip

The access addresses for middleware are all the IP address of this VM.

middleware:
  mysql:
    host: <VM IP address>
    port: 3306
    username: root
    password: "123456"
    dbname: lowcode
    dbRuntimeName: lcruntime
  s3:
    ## Do not include the http or https protocol name; fill in the protocol name [http or https] in the scheme field
    endpoint: <VM IP address>
    port: 9000
    scheme: http
    accessKey: admin
    secretKey: admin@123456
    insecureSkipVerify: false
    defaultBucket: lowcode
    cloudStorageBucket: lowcode-storage
    ciSource: lowcode-ci-source
    ## Fill in according to your actual situation
    region: us-east-1
    pathStyle: true
  build:
    enabled: true
    type: "gitness"
    gitness:
      host: "http://<VM IP address>:3000"
      secretId: "admin"
      secretKey: "admin"
      proxy: "<WeDa access domain name, which must be accessible from the current machine. If no DNS resolution is available, configure the intranet resolution Host>"
      projectName: "lowcode"
      repoName: "software"