📝 Best Practice from the Smart Home Industry: Migration from Docker Swarm to Kubernetes. Explore this journey → close
  • English
    • English
    • 简体中文
    1. 1.Experience account: demo1 / Demo123
    2. 2.This account is only allowed to view parts of UI
    3. 3.It's recommended that install KubeSphere in your environment

You are viewing documentation for KubeSphere version:v3.0.0

KubeSphere v3.0.0 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.

  1. Documentation / 
  2. DevOps User Guide / 
  3. Use DevOps / 
  4. Set a CI Node for Dependency Caching

DevOps User Guide

Last updated:
    Edit

    Set a CI Node for Dependency Caching

    Generally, different dependencies need to be pulled as applications are being built. This may cause some issues such as long pulling time and network instability, further resulting in build failures. To provide your pipeline with a more enabling and stable environment, you can configure a node or a group of nodes specifically for continuous integration (CI). These CI nodes can speed up the building process by using caches.

    This tutorial demonstrates how you set CI nodes so that KubeSphere schedules tasks of pipelines and S2I/B2I builds to these nodes.

    Prerequisites

    You need an account granted a role including the authorization of Clusters Management. For example, you can log in to the console as admin directly or create a new role with the authorization and assign it to an account.

    Label a CI Node

    1. Click Platform in the top left corner and select Clusters Management.

      clusters-management

    2. If you have enabled the multi-cluster feature with member clusters imported, you can select a specific cluster to view its nodes. If you have not enabled the feature, refer to the next step directly.

    3. Navigate to Cluster Nodes under Nodes, where you can see existing nodes in the current cluster.

      Node Management

    4. Choose a node from the list to run CI tasks. For example, select node2 here and click it to go to its detail page. Click More and select Edit Labels.

      Select CI Node

    5. In the dialog that appears, click Add Labels. Add a new label with key node-role.kubernetes.io/worker and value ci, and click Save.

      Add CI Label

      Note

      The node may already have the key without a value. You can input the value ci directly.

    Add a Taint to a CI Node

    Basically, pipelines and S2I/B2I workflows will be scheduled to this node according to node affinity. If you want to make the node a dedicated one for CI tasks, which means other workloads are not allowed to be scheduled to it, you can add a taint to it.

    1. Click More and select Taint Management.

      Select CI Node

    2. Click Add Taint and enter a key node.kubernetes.io/ci without specifying a value. You can choose NoSchedule or PreferNoSchedule based on your needs.

      Add Taint

    3. Click Save. KubeSphere will schedule tasks according to the taint you set. You can go back to work on your DevOps pipeline now.

      Taint Result

      Tip

      This tutorial also covers the operation related to node management. For detailed information, see Node Management.
    Previous Previous : Set Email Server for KubeSphere Pipelines
    What’s on this Page