KubeSphere DevOps System
The KubeSphere DevOps System is designed for CI/CD workflows in Kubernetes. Based on Jenkins, it provides one-stop solutions to help both development and Ops teams build, test and publish apps to Kubernetes in a straight-forward way. It also features plugin management, Binary-to-Image (B2I), Source-to-Image (S2I), code dependency caching, code quality analysis, pipeline logging, and more.
The DevOps System offers an automated environment for users as apps can be automatically released to the same platform. It is also compatible with third-party private image registries (for example, Harbor) and code repositories (for example, GitLab/GitHub/SVN/BitBucket). As such, it creates excellent user experience by providing users with comprehensive, visualized CI/CD pipelines which are extremely useful in air-gapped environments.
For more information, see DevOps User Guide.
Enable DevOps Before Installation
Installing on Linux
When you implement multi-node installation of KubeSphere on Linux, you need to create a configuration file, which lists all KubeSphere components.
In the tutorial of Installing KubeSphere on Linux, you create a default file
config-sample.yaml
. Modify the file by running the following command:vi config-sample.yaml
Note
If you adopt All-in-One Installation, you do not need to create aconfig-sample.yaml
file as you can create a cluster directly. Generally, the all-in-one mode is for users who are new to KubeSphere and look to get familiar with the system. If you want to enable DevOps in this mode (for example, for testing purposes), refer to the following section to see how DevOps can be installed after installation.In this file, search for
devops
and changefalse
totrue
forenabled
. Save the file after you finish.devops: enabled: true # Change "false" to "true".
Create a cluster using the configuration file:
./kk create cluster -f config-sample.yaml
Installing on Kubernetes
As you install KubeSphere on Kubernetes, you can enable KubeSphere DevOps first in the cluster-configuration.yaml file.
Download the file cluster-configuration.yaml and edit it.
vi cluster-configuration.yaml
In this local
cluster-configuration.yaml
file, search fordevops
and enable DevOps by changingfalse
totrue
forenabled
. Save the file after you finish.devops: enabled: true # Change "false" to "true".
Run the following commands to start installation:
kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.3.2/kubesphere-installer.yaml kubectl apply -f cluster-configuration.yaml
Enable DevOps After Installation
Log in to the console as
admin
. Click Platform in the upper-left corner and select Cluster Management.Click CRDs and enter
clusterconfiguration
in the search bar. Click the result to view its detail page.Info
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.In Custom Resources, click on the right of
ks-installer
and select Edit YAML.In this YAML file, search for
devops
and changefalse
totrue
forenabled
. After you finish, click OK in the lower-right corner to save the configuration.devops: enabled: true # Change "false" to "true".
Use the web kubectl to check the installation process by running the following command:
kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l 'app in (ks-install, ks-installer)' -o jsonpath='{.items[0].metadata.name}') -f
Note
You can find the web kubectl tool by clicking in the lower-right corner of the console.
Verify the Installation of the Component
Run the following command to check the status of Pods:
kubectl get pod -n kubesphere-devops-system
The output may look as follows if the component runs successfully:
NAME READY STATUS RESTARTS AGE
devops-jenkins-5cbbfbb975-hjnll 1/1 Running 0 40m
s2ioperator-0 1/1 Running 0 41m
Feedback
Was this page Helpful?
Receive the latest news, articles and updates from KubeSphere
Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.