LTS

    Innovation Version

      openEuler Native Development Environment Cluster Deployment

      This document describes how to deploy a Kubernetes cluster using kubeadm, set up a Kubernetes+iSulad environment, and deploy GitLab Runner in the environment to deploy an openEuler native development environment cluster.

      The following scenarios are covered in this doucment:

      Scenario 1: openEuler native deployment CI/CD based on GitLab CI/CD Scenario 2: openEuler native development cluster managed by GitLab CI/CD

      Scenario 1 contains the following steps:

      1. Kubenetes+iSulad environment deployment
      2. GitLab deployment
      3. GitLab Runner deployment and tesing

      Scenario 1 contains the following steps:

      1. Kubenetes+iSulad environment deployment
      2. GitLab Runner deployment and testing

      Note: All operations in this document are executed with root privileges.

      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备份